Novelcraft

Fully autonomous book author. Creates complete novels from idea to finished PDF/EPUB. Modular workflow with standardized config schema v3.2: Concept → Option...

This skill appears to be what it claims (an autonomous novel author), but exercise caution before giving it autonomous control. - Start in 'step-by-step' mode (the docs recommend this) and test with a tiny project. - Review SECURITY.md and module-images.md before enabling images. Do not enable external image providers (API endpoints) or paste secrets into project files until you know where data is sent. - Confirm whether you need pandoc/xelatex for your use case; the registry metadata omits them but the docs reference them for PDF/EPUB generation. - Note the skill uses powerful agent APIs (list/kill/spawn subagents and write locks/manifests). Ensure you understand and trust this behavior before running in autonomous mode. - Point out to the maintainer the contradictory guidance (e.g., 'DO NOT poll sessions_list' vs example code that lists subagents) and ask for clearer, minimal privileges for subagent management. - If you plan to use image generation, configure providers to local/offline endpoints where possible and keep API keys in an external secret store (not in project-manifest or module-*.md files). If you want, I can list the exact doc lines that contradict each other and propose a minimal checklist to safely test the skill.

Type: OpenClaw Skill Name: novelcraft Version: 3.2.3 NovelCraft is a comprehensive autonomous book-authoring skill that utilizes a modular subagent architecture to handle concept generation, sequential chapter writing, and document publication. The skill is well-documented, featuring a detailed security guide (SECURITY.md), a quality-control scoring system, and clear instructions for error recovery and subagent management. While it requires significant file system access and optional network connectivity for image generation, these behaviors are strictly aligned with its stated purpose and include safety features such as disabling images by default. The presence of hardcoded local paths (e.g., /home/felix/) and a local IP address (192.168.2.150) in the templates appears to be a lack of portability or a placeholder from the developer's environment rather than a sign of malicious intent.