Novel Writer Skill

Novel writing assistant for Chinese or English fiction. Use when the user wants to write, plan, continue, revise, or manage a novel, especially long-form fic...

Security Scan

Instruction-only novel-writing skill whose declared purpose, files, and runtime instructions are coherent and proportionate; it requests no credentials or system access and has no install steps.

Purpose & Capability

The name, description, skill.yaml triggers, SKILL.md workflow, and provided templates all align with a long-form fiction assistant. Nothing in the bundle requests unrelated capabilities (no cloud credentials, no binaries, no config paths).

Instruction Scope

SKILL.md stays within the stated purpose: topic selection, building a novel bible, chapter drafting, continuity tracking, continuation, and revision. It asks the agent to reconstruct context only from the user's novel bible/outline/chapter summaries (which are user-provided) and to use included templates. It does not instruct reading system files, environment variables, or contacting external endpoints.

Install Mechanism

There is no install spec and no code files to write or execute. This lowest-risk model (instruction-only) means nothing will be downloaded or installed by the skill itself.

Credentials

The skill declares no required environment variables, no primary credential, and no config paths. Nothing requests secrets or unrelated credentials.

Persistence & Privilege

always is false, permissions list is empty, and disable-model-invocation is default (false) — standard behavior. The skill does not request persistent privileged presence or modify other skills or system settings.

Assessment

This skill appears coherent and low-risk: it only contains instructions and templates for writing novels and asks for no credentials or system access. Things to consider before installing: (1) provenance — the source/homepage is unknown and the author string is local to the package (no external homepage); if provenance matters to you, prefer skills from known authors. (2) Privacy — any unpublished text or plot you paste will be processed by the agent and may be logged by the platform; avoid pasting sensitive personal data. (3) Backups — the skill recommends keeping a living novel bible/ledger; store those documents where you normally keep work you want to preserve. No technical red flags were found, but if you later see instructions that ask the agent to read local files, use credentials, or contact external URLs, treat that as suspicious and re-evaluate.

Novel Writer

Core Goal

Help the user create coherent long-form fiction through a controlled writing pipeline:

1. Let the user choose the topic and direction.
2. Build a durable novel bible before drafting.
3. Draft chapter by chapter with continuity checks.
4. Maintain character, timeline, clue, setting, and unresolved-thread ledgers.
5. Revise without breaking established facts.

Default to Chinese output unless the user asks for another language.

Operating Rules

• Do not start writing the main text until the topic, genre, protagonist, central conflict, tone, and target length are clear.
• If the user only says "write a novel" or gives a vague idea, offer 3-5 sharply different topic directions and ask them to choose.
• For long novels, create or update a "novel bible" before drafting chapters.
• Keep every chapter connected to prior facts, character goals, causal consequences, and unresolved promises.
• Do not resolve major conflicts too early unless the user requests a short story or novella.
• Track continuity explicitly after each chapter.
• When continuing a novel, first ask for or infer the latest outline, previous chapter summary, continuity ledger, and target for the next chapter.
• Preserve the user's preferred style, POV, tense, genre conventions, taboo content limits, and pacing preferences.

Workflow

Phase 1: Topic Selection

If the user has not chosen a topic, present a compact menu:

• 3-5 novel premises with different genres or conflicts.
• For each premise, include genre, hook, protagonist, core conflict, and long-form potential.
• Ask the user to pick one or combine elements.

If the user already has a topic, refine it with only the missing essentials:

• genre/subgenre
• target length: short, novella, long novel, web serial
• protagonist
• core desire
• main opposition
• tone and style
• preferred POV

Phase 2: Novel Bible

Create a durable planning document before long-form drafting. Include:

• title candidates
• logline
• genre promise
• theme
• protagonist profile
• major character cards
• relationship map
• world rules or social context
• central conflict
• act structure or volume structure
• chapter arc list
• continuity ledger
• unresolved-thread ledger

Use references/templates.md when a concrete format is useful.

Phase 3: Chapter Drafting

Before drafting each chapter, state:

• chapter objective
• POV character
• scene beats
• emotional turn
• new information revealed
• continuity constraints

Then write the chapter in polished prose. After the chapter, update:

• one-paragraph chapter summary
• changed character states
• new facts
• unresolved threads
• foreshadowing planted
• continuity risks

Phase 4: Continuation

When the user asks to continue:

1. Reconstruct the current state from the latest novel bible, outline, and chapter summaries.
2. Identify the next causal consequence, not just the next event.
3. Draft the next chapter or scene.
4. Update the continuity ledger.

If prior context is insufficient, ask for the last chapter or current outline before producing canonical continuation.

Phase 5: Revision

For revisions, preserve continuity first. When changing earlier material, report what downstream facts must also change.

Common revision tasks:

• strengthen hook
• deepen character motivation
• fix plot holes
• improve pacing
• enrich sensory detail
• make dialogue more distinct
• align tone with genre
• compress or expand scenes

Output Discipline

• For planning tasks, use structured Markdown.
• For prose drafts, write immersive fiction first, then a short continuity update.
• Do not over-explain craft theory unless the user asks.
• For long projects, recommend saving the novel bible and chapter ledger as living documents.