· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Changkyun Kim v0.2.0
Write continuity-safe novels
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Create a new novel workspace and help me define its premise.
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Initialize a Markdown novel workspace, develop settings, characters, materials, plots, and outlines, apply genre-aware storytelling strategies, review outlines and manuscripts analytically, control continuity and reader understanding, create visual assets, and finish with a validated EPUB.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: analytical-review description: Review novel outlines, drafted chapters, full manuscripts, and prior revision findings as an independent analytical editor. Use when the author explicitly requests critique, developmental review, work examination, line editing, proofreading, whole-manuscript review, or regression verification, and when an explicitly fully autonomous workflow covers the complete novel lifecycle from initial planning through publication. Produce an intent-aware, evidence-backed report with Overall Assessment, Work Examination, and Line Editing or Proofreading sections while remaining read-only by default. Do not invoke this skill automatically for ordinary planning, drafting, revision, continuity validation, EPUB export, build, regeneration, packaging, validation, or publication requests. --- # Analytical Review Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. Keep `--project-root` pointed at the active novel workspace, not at the skill or plugin installation. ## Operating Contract Adopt an independent reviewer role. Diagnose the work without changing it. Do not edit outlines, chapters, canon, the story ledger, or generated output during a review-only request. If the author requests both review and revision, finish and present the diagnosis before applying selected findings. Use `novel-story-telling` for the revision phase and preserve finding IDs across the handoff. Write all internal instructions, temporary schemas, and script inputs in English. Return the review in this order of precedence: 1. the language explicitly requested by the author; 2. `project.md` `language`; 3. `style/000.style-guide.md` `language`; 4. the dominant language of the reviewed source. Localize report headings naturally while preserving the semantic section order defined in [report-contract.md](references/report-contract.md). For Korean output, use the canonical labels `작품 총평`, `작품 검토`, and `문면 교열`. Treat the current manuscript and review response as private runtime material. Use relative source anchors and only the shortest excerpt needed for evidence. Do not copy manuscript prose or review output into the project, plugin, examples, fixtures, or generated package. Save a report only when the author explicitly requests a file and confirms its destination. ## 1. Confirm Authorization, Mode, And Scope Read [review-modes.md](references/review-modes.md). Select exactly one mode: - `outline`: planned story direction before prose exists; - `chapter`: one or more explicitly named Drafts; - `manuscript`: every numbered publishable chapter plus cross-chapter synthesis; - `regression`: bounded verification of earlier findings after revision. Invoke this skill only when: - the author explicitly requests review, critique, line editing, proofreading, developmental feedback, or verification of prior findings; or - the author explicitly delegates the complete autonomous lifecycle from initial planning through final publication. Do not infer review authorization from an ordinary planning, drafting, revision, validation, export, build, package, or publish request. `Review and publish` authorizes review but not automatic revision. `Proofread and fix` authorizes both phases; keep them distinct. Confirm the requested source scope. For a chapter request, identify exact chapter numbers or relative paths. For regression mode, require the prior finding IDs, dispositions, and changed units. ## 2. Orient To The Work Read: - `AGENTS.md`; - `project.md`; - `style/000.style-guide.md`; - `plot/000.master-plot.md`; - `outlines/000.master-outline.md`; - the sources in the declared review scope; - only the linked character, world, material, MacGuffin, and plot files needed to establish intent or continuity. Do not load every source file by default. Use author-side sources to understand intent, rules, and hidden truth. Use only publishable `## Draft` text to claim that a reader
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 7 — file references are metadata, not package contents.
--- name: create-character description: Create character source files for this novel project. Use when the user wants to invent, refine, name, or save a fictional character into characters/ as Markdown with YAML frontmatter, especially from role, personality, setting, era, region, language, relationships, motives, secrets, or plot function. --- # Create Character ## Overview Use this skill to turn a rough character brief into a complete `characters/*.md` source file for this novel project. Always follow the project's `AGENTS.md` and `characters/_template.md`. Keep the process interactive: refine the character first, then run a naming loop, then write the file only after the user confirms the final direction. Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. This keeps the same skill usable from either the repository-local skill tree or the Novelist plugin. ## Workflow ### 1. Gather And Reflect The Brief Read existing context before asking questions: - `AGENTS.md` - `project.md` - `characters/_template.md` - Existing files in `characters/` - Relevant `plot/`, `outlines/`, `world/`, `materials/`, or `macguffins/` files when the user references them Restate the supplied role, character traits, and setting in Korean. Include: - story role - social role or occupation - personality and behavioral texture - era, region, class, language, nationality, and cultural background - gender, including whether the character is gender-neutral - relationship or plot function - secrets, desires, conflicts, or contradictions if present Ask what the user wants to add, remove, or sharpen. Continue this prompt loop until the user says it is enough or gives enough detail to proceed. Do not create the character file during this stage. ### 2. Recommend Names After the brief is sufficiently refined, propose about 10 names with short reasons. Naming rules: - If the character is Korean or lives as a Korean character in South Korea, recommend plausible Korean names in Hangul with family name and given name. - If the setting gives a specific Korean era, region, class, or dialect background, reflect that context in the name choice and explain the reasoning. - If the character is not Korean, keep both the original-language name and the Korean reading for use in the novel. - If the original script is relevant, include it. Example: `Aleksandr Mikhailov / 알렉산드르 미하일로프`. - If only a romanized original is appropriate, still include a Korean reading. - Avoid copying the exact identity of a real living person unless the user explicitly requests a real person. - Avoid joke names, overly symbolic names, and famous-name collisions unless the user asks for them. For each option, show: - displayed Korean name or Korean reading - original name when non-Korean - name language or cultural context - reason it fits the role, personality, and setting Ask the user to choose a name, request revisions, or provide a new naming direction. Continue this prompt loop until one final name is selected. ### 3. Build The Character Sheet Create a complete character sheet using the selected name and refined brief. Required frontmatter keys: ```yaml id: char-ascii-slug type: character name: "김하나" original_name: "김하나" korean_reading: "김하나" name_language: ko name_context: "현대 대한민국" aliases: [] role: "" status: seed age: "" gender: "" pronouns: "" first_appearance: "" last_seen: "" relationships: [] wants: [] needs: [] conflicts: [] secrets: [] related_materials: [] related_macguffins: [] plot_threads: [] created: YYYY-MM-DD updated: YYYY-MM-DD tags: [] ``` Use an ASCII filesystem slug, such as `kim-hana`, `alexandr-mikhailov`, or `old-palace-guard`. The file path must be `characters/<slug>.md`, and `id` must be `char-<slug>`. Set `gender` explicitly when the user provides or confirms it. If the character is gender-neutral, use `gender: "성별 중립"` and keep pronouns or honorific usage consistent with the setting. I
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
--- name: create-material description: Create story material source files for this novel project. Use when the user wants to generate, refine, or save raw novel material such as motifs, objects, scene seeds, dialogue seeds, research notes, themes, images, conflicts, clues, or reusable ideas into materials/ as Markdown with YAML frontmatter. --- # Create Material ## Overview Use this skill to turn a rough story-material prompt into a complete `materials/*.md` source file. Always follow `AGENTS.md` and `materials/_template.md`. Generate useful seed material from the prompt, ask for missing information and intended story use, revise from feedback, then write only after confirmation. Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. This keeps the same skill usable from either the repository-local skill tree or the Novelist plugin. ## Workflow ### 1. Read Context Read: - `AGENTS.md` - `project.md` - `materials/_template.md` - Existing files in `materials/` - Relevant `characters/`, `macguffins/`, `plot/`, `outlines/`, and `world/` files if referenced ### 2. Generate A Material Draft From the user's prompt, infer a compact first-pass material note in Korean. Include: - material category, such as `scene-seed`, `motif`, `object`, `line`, `research`, `theme`, `image`, `conflict`, or `clue` - raw idea - possible story use - related characters, MacGuffins, plot threads, or settings - whether it is canonical yet - constraints, risks, or questions - open decisions the user should make Mark inferred items clearly. Keep uncertain ideas as `status: seed` and `canonical: false`. ### 3. Ask For Direction Ask the user what role this material should play: - background texture or major plot driver - literal object or metaphor - one-scene use or recurring motif - clue, red herring, image system, dialogue seed, or research note - canonical fact or scratch seed Continue the feedback loop until the user says it is enough or gives enough detail to save. ### 4. Build The Material File Use a filesystem-safe ASCII slug. Save to `materials/<slug>.md`; `id` must be `material-<slug>`. Required frontmatter: ```yaml id: material-ascii-slug type: material title: "" category: scene-seed status: seed source: "" canonical: false related_characters: [] related_macguffins: [] plot_threads: [] used_in_chapters: [] created: YYYY-MM-DD updated: YYYY-MM-DD tags: [] ``` The Markdown body must include: - `# <title>` - `## Idea` - `## Story Use` - `## Notes` ### 5. Write And Verify Prefer the bundled script: ```bash python3 "<skill-dir>/scripts/write_material.py" --input /path/to/material.json --project-root . ``` Use a temporary JSON file with final confirmed data. The script writes `materials/<slug>.md`, refuses invalid slugs, and refuses to overwrite existing files unless `--force` is passed. After writing, verify frontmatter delimiters, `type: material`, matching `id`, and `git status --short`. Do not commit unless the user asks.
Referenced files: 2 — file references are metadata, not package contents.
--- name: create-novel-project description: Initialize a safe, self-contained Markdown novel workspace from the Novelist plugin scaffold. Use when the user wants to start, scaffold, bootstrap, or create a new novel project with source directories, templates, continuity rules, visual guidance, and EPUB output conventions. --- # Create Novel Project ## Operating Contract Create a novel source workspace from the scaffold bundled with this plugin. The scaffold includes source directories, YAML-frontmatter templates, manuscript markup rules, visual direction, and generated-output boundaries. It does not copy another set of Agent Skills into the project; the installed Novelist plugin continues to provide them. Before running the bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. ## Workflow 1. Resolve the destination from the user's explicit path. If no path was given, use the current directory only when it is clearly the intended workspace; otherwise ask for the destination. 2. Gather a working title and BCP 47-style language tag when the user supplied them. Both are optional: the defaults remain `Untitled Novel` and `ko`. 3. Inspect the destination before writing. Preserve unrelated existing files. 4. Run the bundled initializer: ```bash python3 "<skill-dir>/scripts/create_novel_project.py" \ --project-root /absolute/path/to/novel \ --title "Working Title" \ --language ko ``` 5. Do not pass `--force` merely because the destination exists. The initializer performs a complete collision preflight and writes nothing when a scaffold file would be overwritten. Use `--force` only after the user explicitly asks to replace the plugin-managed scaffold files. 6. Verify `project.md`, `AGENTS.md`, the source directories and templates, and `published/.gitignore`. Run `git status --short` when the destination is inside a Git repository. 7. Summarize the created paths and suggest the next relevant plugin skill, such as `create-setting`, `create-character`, or `create-plot`. Let the host apply its own invocation syntax. ## Safety Rules - Never initialize into the plugin installation itself. - Never delete unrelated destination files. - Never copy `.git`, `.codex`, generated EPUB output, or project-local skill duplicates into the new workspace. - Treat the copied Markdown files as canonical source and `published/` as generated output. - Do not commit unless the user asks.
Referenced files: 3 — file references are metadata, not package contents.
--- name: create-plot description: Create whole-novel plot and plot-thread source files for this novel project. Use when the user wants to generate, refine, structure, or save a central plot, act structure, promise, pressure, reversals, turns, reveals, or payoffs into plot/ as Markdown with YAML frontmatter. --- # Create Plot ## Overview Use this skill to turn a rough plot prompt into a complete `plot/*.md` source file. Always follow `AGENTS.md` and `plot/_template.md`. Generate a workable plot skeleton from the user's prompt, ask for missing information and desired direction, revise through feedback, then write only after confirmation. Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. This keeps the same skill usable from either the repository-local skill tree or the Novelist plugin. ## Workflow ### 1. Read Context Read: - `AGENTS.md` - `project.md` - `plot/_template.md` - `plot/000.master-plot.md` - Existing files in `plot/` - Relevant `outlines/`, `world/`, `characters/`, `materials/`, and `macguffins/` files if referenced ### 2. Generate A Plot Draft From the user's prompt, infer a compact first-pass plot in Korean. Include: - story promise - protagonist pressure and opposition - inciting incident - core conflict - act or sequence shape - midpoint reversal - lowest point - climax choice - resolution shape - setups, reveals, and payoffs - open questions and missing decisions Mark inferred items clearly. Do not lock major canon facts without user confirmation. ### 3. Ask For Direction Ask the user what to strengthen, remove, or decide. Focus on plot decisions with real consequences: - emotional ending vs ironic ending - external conflict vs internal conflict - mystery-first, thriller-first, romance-first, or literary-first structure - single protagonist vs ensemble pressure - reveal timing and whether the reader knows more than the characters Continue the feedback loop until the user says it is enough or gives enough detail to save. ### 4. Build The Plot File Use a filesystem-safe ASCII slug. Save to `plot/<slug>.md`; `id` must be `plot-<slug>`. Required frontmatter: ```yaml id: plot-ascii-slug type: plot title: "" scope: novel status: seed starts_in: "" turns_in: [] pays_off_in: "" characters: [] materials: [] macguffins: [] created: YYYY-MM-DD updated: YYYY-MM-DD tags: [] ``` Use `scope: novel` for the whole-book plot and `scope: thread` for a subplot or plot thread. The Markdown body must include: - `# <title>` - `## Promise` - `## Pressure` - `## Turns` ### 5. Write And Verify Prefer the bundled script: ```bash python3 "<skill-dir>/scripts/write_plot.py" --input /path/to/plot.json --project-root . ``` Use a temporary JSON file with final confirmed data. The script writes `plot/<slug>.md`, refuses invalid slugs, and refuses to overwrite existing files unless `--force` is passed. After writing, verify frontmatter delimiters, `type: plot`, matching `id`, and `git status --short`. Do not commit unless the user asks.
Referenced files: 2 — file references are metadata, not package contents.
--- name: create-setting description: Create whole-novel setting and worldbuilding source files for this novel project. Use when the user wants to generate, refine, or save a novel setting, era, region, social order, locations, rules, atmosphere, constraints, or continuity facts into world/ as Markdown with YAML frontmatter. --- # Create Setting ## Overview Use this skill to turn a rough novel-setting prompt into a complete `world/*.md` source file. Always follow `AGENTS.md` and `world/_template.md`. Generate useful defaults from the user's prompt, but keep the process interactive: reflect the inferred setting, ask for missing information and direction, revise from feedback, then write only after the user confirms. Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. This keeps the same skill usable from either the repository-local skill tree or the Novelist plugin. ## Workflow ### 1. Read Context Read: - `AGENTS.md` - `project.md` - `world/_template.md` - Existing files in `world/` - Relevant `plot/`, `outlines/`, `materials/`, `macguffins/`, and `characters/` files if the prompt references them ### 2. Generate A Setting Draft From the user's prompt, infer a compact first-pass setting in Korean. Include: - era and time scale - primary region and key locations - social order, institutions, class pressure, and power structure - material culture and technology level - atmosphere, sensory palette, and recurring visual motifs - rules or constraints that affect plot - continuity facts that should not drift - open questions and missing decisions Mark inferred items clearly. Do not present guesses as fixed canon. ### 3. Ask For Direction Ask the user what to add, remove, sharpen, or decide. The question must focus on missing information and authorial direction, not on generic brainstorming. Good prompts: - "시대는 조선 후기 그대로 둘까요, 아니면 가상의 왕조로 비틀까요?" - "이 세계의 핵심 압박을 정치, 가족, 종교, 경제 중 어디에 두면 좋을까요?" - "현실 고증을 강하게 가져갈지, 분위기 우선으로 변형할지 선택해주세요." Continue the feedback loop until the user says it is enough or gives enough detail to save. ### 4. Build The Setting File Use a filesystem-safe ASCII slug. Save to `world/<slug>.md`; `id` must be `world-<slug>`. Required frontmatter: ```yaml id: world-ascii-slug type: world title: "" category: setting status: seed time_period: "" locations: [] rules: [] related_characters: [] related_materials: [] used_in_chapters: [] created: YYYY-MM-DD updated: YYYY-MM-DD tags: [] ``` The Markdown body must include: - `# <title>` - `## Description` - `## Story Pressure` - `## Continuity` ### 5. Write And Verify Prefer the bundled script: ```bash python3 "<skill-dir>/scripts/write_setting.py" --input /path/to/setting.json --project-root . ``` Use a temporary JSON file with final confirmed data. The script writes `world/<slug>.md`, refuses invalid slugs, and refuses to overwrite existing files unless `--force` is passed. After writing, verify frontmatter delimiters, `type: world`, matching `id`, and `git status --short`. Do not commit unless the user asks.
Referenced files: 2 — file references are metadata, not package contents.
--- name: create-visual-asset description: Create cover and illustration image assets for this novel project with an available raster image provider. Use when the user wants to plan, generate, refine, or save a book cover, chapter illustration, spot illustration, visual motif, or image prompt while preserving a consistent visual style across assets. --- # Create Visual Asset ## Overview Use this skill to create project-bound cover and illustration assets for the novel. Always preserve visual consistency by reading `style/visual-style-guide.md` first. Detect the image-generation capabilities available in the current host, then use the matching guide: - Codex: `references/codex-image-generation.md` - Claude Code: `references/claude-image-generation.md` - Antigravity CLI: `references/antigravity-image-generation.md` - External API or CLI provider: `references/external-image-provider.md` Save final project-bound assets under `assets/cover/` or `assets/illustrations/`; never leave a referenced asset only in a provider's default output location. ## Required Context Read before generating: - `AGENTS.md` - `project.md` - `style/visual-style-guide.md` - relevant `chapters/*.md`, `outlines/`, `plot/`, `world/`, `characters/`, `materials/`, and `macguffins/` files for the requested asset - existing files in `assets/cover/` and `assets/illustrations/` If `style/visual-style-guide.md` is incomplete, ask the user for missing visual direction before generating a final asset. ## Workflow ### 1. Identify Asset Type Classify the request as one of: - `cover`: front cover image for EPUB packaging - `chapter-illustration`: full-width or full-page illustration tied to a chapter - `spot-illustration`: smaller image embedded within a chapter - `motif`: reusable visual symbol, object, or atmospheric plate - `reference`: visual exploration not yet used in the manuscript Confirm the intended destination and filename slug before saving. ### 2. Gather Direction Summarize the likely image in Korean: - subject - narrative moment or symbolic function - setting and time period - characters shown or deliberately omitted - composition and crop - mood, lighting, palette, and texture - continuity constraints from source files - whether text should be included Ask for missing direction when it affects the image. For covers, ask about tone, central image, and whether the title/author text should be left out for later typography. Prefer no generated text unless the user explicitly asks for it. ### 3. Build A Style-Locked Prompt Use the visual style guide as the stable base. Keep the prompt concise but specific: ```text Use case: illustration-story Asset type: <cover|chapter-illustration|spot-illustration|motif|reference> Primary request: <specific image> Story context: <chapter/plot/world context> Style/medium: <from style/visual-style-guide.md> Composition/framing: <crop, subject placement, negative space> Lighting/mood: <from style guide plus asset-specific mood> Color palette: <from style guide> Materials/textures: <paper, ink, grain, brush, lens, etc.> Continuity constraints: <must match story facts> Text: no text, no title, no watermark unless explicitly requested Avoid: <style guide avoid list plus asset-specific avoid list> ``` ### 4. Select And Invoke A Raster Provider Inspect the tools actually available in the current agent host. Prefer, in order: 1. a verified built-in raster image generator; 2. a configured image-generation MCP server or agent tool; 3. an author-approved external API or CLI adapter. Do not infer image-generation capability from image input, image analysis, or generic file tools. Do not substitute SVG, HTML, or placeholder art. For project-bound assets: 1. Generate the image with the selected raster provider. 2. Inspect the result for style, subject, composition, and continuity. 3. Iterate only with targeted changes. 4. Move or copy the final selected image into the project: - cover: `assets/cover/<slug>.<ex
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 7 — file references are metadata, not package contents.
--- name: novel-story-telling description: Design and control whole-novel storytelling, reader mental-model progression, chapter-to-chapter flow, conflict escalation and resolution, reveals, foreshadowing, continuity, safe chapter-file creation, and next-chapter handoffs for this Markdown novel repository. Use when planning, drafting, or revising story structure, modeling what a target reader knows, infers, misreads, or still asks at each story turn, auditing cohesion or reader orientation, preparing or writing the next chapter from prior context, creating a template-conformant chapter under chapters/, checking contradictions, maintaining story-state summaries, selecting genre-specific narrative devices, or auditing character, timeline, world-rule, clue, MacGuffin, and plot-thread continuity. --- # Novel Story Telling Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`. Keep `--project-root` pointed at the active novel workspace, not at the skill or plugin installation. ## Operating Contract Treat `chapters/` as manuscript canon and all other source directories as planning and continuity evidence. Follow `AGENTS.md`. Never edit `published/` as source. Write all agent instructions, temporary prompts, schemas, and script inputs in English. Write manuscript prose and author-facing creative output in this order of precedence: 1. the language explicitly requested by the author; 2. `project.md` `language`; 3. `style/000.style-guide.md` `language`; 4. the dominant language of recent chapters. Preserve names, honorifics, invented terms, and spelling from canonical files. Do not translate them unless requested. Resolve conflicts by authority: explicit author direction > `final` source > `revision` source > latest manuscript fact > `draft` source > outline or seed. Report unresolved conflicts; do not silently choose or invent canon. ## Analytical Review Routing Boundary Keep analytical review separate from ordinary planning, drafting, and revision. Do not invoke `analytical-review` unless the author explicitly requests critique/review or explicitly delegates the complete autonomous novel lifecycle from initial planning through publication. For that fully autonomous start-to-publication request only, after all chapters are drafted and before calling `publish-novel`: 1. run whole-manuscript `analytical-review`; 2. record each material finding as `apply`, `defer`, or `reject` with a concise rationale; 3. apply selected findings through this storytelling workflow and update canon; 4. run one bounded analytical regression review; 5. complete strict continuity validation; 6. call `publish-novel` for deterministic packaging. An ordinary request to finish remaining chapters, revise known material, or publish an existing manuscript does not by itself authorize this loop. If the author explicitly asks for review and revision together, keep diagnosis and application distinct and preserve finding IDs through the handoff. ## Core Workflow ### 1. Orient Read `AGENTS.md`, `project.md`, `style/000.style-guide.md`, `plot/000.master-plot.md`, and `outlines/000.master-outline.md`. Determine: - output language and prose constraints; - current story promise and governing question; - target reader baseline, including genre literacy, prior reader-visible anchors, active questions, and unfamiliar terminology; - target chapter and its irreversible change; - active plot threads, promises, clues, and MacGuffins; - current character knowledge, desire, condition, relationship, and location; - hard world rules and timeline constraints. Do not load every source file into context by default. ### 2. Build A Bounded Context Pack Run: ```bash python3 "<skill-dir>/scripts/build_story_context.py" \ --project-root . \ --chapter <number> \ --query "<POV, location, entities, conflict, or theme>" \ --max-tokens 6000 \ --output-language auto \ --output /tmp/story-context.md ``` Read th
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 15 — file references are metadata, not package contents.
--- name: publish-novel description: Publish this Markdown novel project as a validated EPUB using the skill's bundled packaging script. Use when the author asks to publish, export, build, regenerate, package, or validate the novel or EPUB; when checking publication metadata, chapter readiness, covers, illustrations, generated output, or EPUB integrity; or when coordinating a missing cover before publication. --- # Publish Novel Before running a bundled command, resolve `<skill-dir>` to the absolute directory containing this `SKILL.md`, and resolve `<skills-dir>` to its parent directory. Keep `--project-root` pointed at the active novel workspace, not at the skill or plugin installation. ## Operating Contract Turn an author request such as "Publish this novel" into the complete EPUB workflow. Do not ask the author to type shell commands. Run the bundled script yourself, verify the result, and report the artifact path. Treat Markdown and project assets as canonical source. Treat `published/epub/` and `.epub` files as generated output. Never repair a generated EPUB by hand; update source and republish. Retain both outputs after a successful build. `published/epub/` is the inspectable staging tree, while `published/*.epub` is the ZIP-based EPUB container intended for reading software. Rebuilding may replace the contents of the staging tree, but publication must not delete it after packaging. Interpret `publish` as local EPUB generation only. Do not upload, distribute, email, release, or submit the book to a storefront or external service unless the author explicitly requests that separate action. Do not invoke `analytical-review` merely because the author asks to publish, export, build, regenerate, package, or validate an existing novel. Ordinary publication retains the structural and continuity preflight below. When a fully autonomous start-to-publication workflow was explicitly authorized, the orchestrating storytelling workflow must complete analytical review, finding disposition, revision, and bounded regression review before handing the manuscript to this skill. Keep literary judgment out of `build_epub.py`. ## Workflow ### 1. Read Publication Context Read: - `AGENTS.md` - `project.md` - `published/README.md` - publishable chapter filenames and frontmatter, plus image references needed for packaging - `style/visual-style-guide.md` - existing files under `assets/cover/` and `assets/illustrations/` Preserve the manuscript language and project terminology. Do not load the full prose of every chapter into model context. Let the bundled script stream chapter bodies during rendering. Read chapter prose only when diagnosing a rendering, image, or metadata problem. ### 2. Run Preflight Confirm: - at least one chapter matches `NNN.ascii-slug.md`; - chapter numbers and filenames are in the intended order; - every chapter's H2 sections are exactly `## Synopsis`, `## Draft`, and `## Revision Notes` in that order, with one non-empty, case-sensitive Draft outside fenced code; - the requested manuscript is complete enough to publish; - title, author or pen name, and language are known; - all local Markdown image references inside Draft exist, and the selected cover exists; - the output and staging paths remain under the intended project. Run the story skill's strict structural audit before packaging: ```bash python3 "<skills-dir>/novel-story-telling/scripts/check_continuity.py" \ --project-root . \ --strict ``` Stop on malformed dialogue markup or any other structural error. Canonical dialogue is an exact `*“…”*` range that may stand alone or share a paragraph with narration; interior thought is unquoted `*…*`, and cited wording uses `‘…’`. If any chapter is not `final`, list it and ask for confirmation before publishing unless the author explicitly requests a draft or proof EPUB. If the title is empty or still a placeholder, ask for the publication title. If the author is missing, ask for the author or pen
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Some manifest fields differ or could not be read. The structured report retains the source references.
Package observed Nov 19, 2026.
plugins_6a599e3b00f0819192a964630fc98d27
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.