Chinese Novel Writing System
leenbj/novel-creator-skill
Guides long-form Chinese novel writing from a rough idea through outlines, chapter drafts and quality gates, with file-based memory for a story meant to reach 300万字.
Shared craft rules for long-form fiction writers: scene construction, cause-and-effect characters, deliberate information release and serialized chapter pacing.
Install InkOS Long-Form Narrative Craft
$ npx skills add Narcooo/inkos --skill inkos-long-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Narcooo/inkos inkos-long-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Narcooo/inkos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/inkos-long-writing .claude/skills/inkos-long-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "inkos-long-writing" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing into .claude/skills/inkos-long-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-long-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Narcooo/inkos --skill inkos-long-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Narcooo/inkos inkos-long-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Narcooo/inkos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/skills/inkos-long-writing .agents/skills/inkos-long-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inkos-long-writing" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing into .agents/skills/inkos-long-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-long-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Narcooo/inkos --skill inkos-long-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Narcooo/inkos inkos-long-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Narcooo/inkos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/skills/inkos-long-writing .cursor/skills/inkos-long-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "inkos-long-writing" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing into .cursor/skills/inkos-long-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-long-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Narcooo/inkos.git --path packages/core/skills/inkos-long-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Narcooo/inkos --skill inkos-long-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Narcooo/inkos inkos-long-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Narcooo/inkos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/skills/inkos-long-writing .gemini/skills/inkos-long-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "inkos-long-writing" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing into .gemini/skills/inkos-long-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-long-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Narcooo/inkos inkos-long-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Narcooo/inkos --skill inkos-long-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Narcooo/inkos.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/skills/inkos-long-writing .github/skills/inkos-long-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "inkos-long-writing" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing into .github/skills/inkos-long-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-long-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Narcooo/inkos --skill inkos-long-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Narcooo/inkos inkos-long-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Narcooo/inkos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/skills/inkos-long-writing .opencode/skills/inkos-long-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "inkos-long-writing" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing into .opencode/skills/inkos-long-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-long-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
inkos-long-writing- GitHub stars
- 10k
- Token cost
- ~867 tokens
- SKILL.md length
- 455 words
- Files
- 5 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Shared craft rules for long-form fiction writers: scene construction, cause-and-effect characters, deliberate information release and serialized chapter pacing.
- Drafting a chapter that needs a clear scene objective and real consequences
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Deciding how much backstory to reveal versus hold back in a scene
- Reconciling a changed premise across the outline, chapter plan and already-written prose
What it does
This skill gives the architect, writer, auditor and reviser roles inside InkOS a shared method for long-form narrative. Scenes turn a chapter goal into an immediate objective, resistance, a meaningful turn and consequences that outlast the scene, and character choices follow what each person wants, knows, fears and can afford, with relationships changed by events rather than narrator explanation. Setting and backstory are revealed through action, evidence, dialogue and sensory detail instead of a synopsis, and every passage must move conflict, evidence, emotion, relationship, knowledge, position or future consequence rather than being padded to a length.
Information is controlled deliberately: some active reader questions get answered, others get deepened with concrete evidence, and twists are never manufactured by hiding facts the viewpoint character should already know. Chapters end after a material change or fresh pressure, not a mechanical cliffhanger, and reference material serves only as evidence for craft or facts, never copied as wording, names or scene order. In revision, the smallest layer actually causing a problem gets repaired, premise changes apply consistently across the foundation, chapter plan and prose rather than reviving a deleted idea, and polishing changes only wording and rhythm, preserving events and consequences.
When your agent uses it
- Drafting a chapter that needs a clear scene objective and real consequences
- Deciding how much backstory to reveal versus hold back in a scene
- Reconciling a changed premise across the outline, chapter plan and already-written prose
- Polishing prose without changing the story's events or decisions
Example prompts
- “Draft this chapter so the scene ends with a material change, not a cliffhanger formula.”
- “The author changed the villain's motive. Reconcile the chapter plan and prose with the new premise.”
- “Polish this chapter's prose for rhythm and sensory detail without changing what happens.”
What it can do on your machine
Read from SKILL.md and the folder at commit 8fc2ae5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
InkOS Long-Form Narrative Craft loads about 867 tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 455 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Narcooo/inkos at commit 8fc2ae5, republished under its AGPL-3.0 licence (© Narcooo). 455 words, ~867 tokens.
Download SKILL.mdSave it as
.claude/skills/inkos-long-writing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- inkos-long-writing
- description
- 长篇小说的场景构造、人物因果、信息释放与连载节奏。Used by InkOS long-form workers as their shared craft method.
Long-form narrative craft
Apply this method inside the active architect, writer, auditor, or reviser operation.
- Turn the chapter goal into scenes with an immediate objective, resistance, a meaningful turn, and consequences that survive the scene.
- Let character choices follow what each person wants, knows, fears, and can afford. Relationships change through events, not author explanation.
- Reveal setting and backstory through action, evidence, dialogue, and sensory particulars. Do not replace a scene with a synopsis or analysis.
- Every passage must alter conflict, evidence, emotion, relationship, knowledge, position, or future consequence. Remove padding rather than stretching to a number.
- Control information deliberately: answer some active reader questions, deepen others through concrete evidence, and do not manufacture twists by hiding facts the viewpoint should know.
- Preserve the user's voice, viewpoint, prohibitions, proportions, and current direction. Genre convention is only a default when the governed context is silent.
- End a chapter after a material change or fresh pressure, not with a mechanical cliffhanger formula. Show the after-effect of major payoffs before starting another escalation cycle.
- Use references as evidence for craft or facts only. Do not reproduce source wording, names, scene order, or signature combinations.
- During review or revision, diagnose and repair the smallest layer that actually causes the problem. A formatting failure is not evidence that the prose is bad.
- When the author changes a premise, distinguish retained source facts from superseded generated plans. Apply the latest explicit change consistently to the foundation, chapter plan and prose; an old memo or hook cannot require restoring a deleted premise. Report remaining contradictions between those documents instead of treating the obsolete plan as a new instruction.
- During prose polishing, change only wording, sentence shape, paragraphing, sensory precision, punctuation, and dialogue naturalness. Preserve events, viewpoint, character decisions, information, and consequences. Keep the result close in length and voice to the accepted chapter.
- Prefer concrete verbs, observable reactions, distinct voices, and readable paragraph rhythm over narrator conclusions, repeated hedges, decorative description, or synchronized crowd reactions.
- When reviewing a new foundation, test whether the central conflict can sustain the requested span, the opening creates forward pressure, the world is specific and coherent, major characters differ in motive and voice, and the outline can progress without repeating one beat. For fan fiction or series work, preserve source facts while establishing a real divergence or new narrative space.
- When creating a foundation, connect a visible foreground line to a deeper causal line, give every volume an observable end-state and irreversible change, make character arcs pay a cost, and distinguish dormant seeds from already active promises.
Show full SKILL.md (30 more words)Show less
Load references/foundation-design.md while creating or rebuilding a book foundation. Load references/reader-contract-and-progression.md while planning, writing, reviewing, or revising chapters.
Load references/state-projection.md while observing a completed chapter or settling runtime truth files.
© Narcooo, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in packages/core/skills/inkos-long-writing of Narcooo/inkos.
- SKILL.md
- references/foundation-design.md
- references/reader-contract-and-progression.md
- references/scene-dialogue-and-length-budget.md
- references/state-projection.md
Open the folder on GitHubat commit 8fc2ae5
Compare with similar skills
InkOS Long-Form Narrative Craft next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| InkOS Long-Form Narrative Craft this skillNarcooo/inkos | 10k | — | ~867 | Automated safety check: Pass | AGPL-3.0 | |
| Chinese Novel Writing Systemleenbj/novel-creator-skill | 671 | — | ~3.9k | Automated safety check: Pass | None | |
| Chinese Novelist Chapter WriterPenglongHuang/chinese-novelist-skill | 3.3k | — | ~491 | Automated safety check: Warn | MIT | |
| Sun-Style Restrained Narrative WritingKKKKhazix/sun-style-writing | 403 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Short Web Fiction Writeruu201/character-arc | 583 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Narrative Continuity CriticUfukNode/Noustiny | 181 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Chinese Novelist Chapter Writer
PenglongHuang/chinese-novelist-skill
Writes long Chinese novels chapter by chapter through guided questions, outlining, drafting with cliffhangers and automatic validation, with resumable projects.
Sun-Style Restrained Narrative Writing
KKKKhazix/sun-style-writing
Writes Chinese first-person nonfiction in a restrained plain-description style: short sentences, exact numbers, objects that carry feeling and silence at the peak.
Short Web Fiction Writer
uu201/character-arc
Walks an agent through writing a complete short web novel in Chinese, starting from the emotion the reader should feel and building around one twist.
Narrative Continuity Critic
UfukNode/Noustiny
Grades whether a downstream story beat still holds after an upstream insertion, returning a strict JSON verdict of still_valid, needs_rewrite or must_delete.
Short Web Novel Deconstruction
zenstory-ai/oh-story-claudecode
Breaks down a popular Chinese short story into story core, structure, emotional line, twists and techniques, and saves the analysis as files for a follow-up writing skill.
More from Narcooo/inkos
All 21 skills in this repoInkOS Creative Harness
Narcooo/inkos
Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.
InkOS Story Review
Narcooo/inkos
Reviews chapters or manuscripts against the standard that fits their genre, audience and your own criteria, showing concrete issues and revising only when asked.
Long-Form Fiction Market Research
Narcooo/inkos
Researches the long-form fiction market with sourced evidence: platform differences, comparable works and audience expectations, to inform topic choices for a novel.
Long Story Analysis
Narcooo/inkos
Breaks down a full novel or long sample into story mechanisms and style traits the agent can reuse as craft, without copying names or wording.
InkOS Story Cover Design
Narcooo/inkos
根据作品、平台与用户视觉要求设计或生成封面。Use for story-cover direction and confirmed cover generation.
Semantic Prose Cleanup
Narcooo/inkos
Diagnoses generic, mechanical or AI-sounding fiction prose by its function and effect, then revises it while keeping plot facts and the author's voice.
Related
Categories
Questions about InkOS Long-Form Narrative Craft
What does InkOS Long-Form Narrative Craft do?
Shared craft rules for long-form fiction writers: scene construction, cause-and-effect characters, deliberate information release and serialized chapter pacing. This skill gives the architect, writer, auditor and reviser roles inside InkOS a shared method for long-form narrative. Scenes turn a chapter goal into an immediate objective, resistance, a meaningful turn and consequences that outlast the scene, and character choices follow what each person wants, knows, fears and can afford, with relationships changed by events rather than narrator explanation.
When should I use InkOS Long-Form Narrative Craft?
InkOS Long-Form Narrative Craft fits situations like: drafting a chapter that needs a clear scene objective and real consequences; deciding how much backstory to reveal versus hold back in a scene; reconciling a changed premise across the outline, chapter plan and already-written prose; polishing prose without changing the story's events or decisions.
How do I install InkOS Long-Form Narrative Craft in Claude Code?
Run `npx skills add Narcooo/inkos --skill inkos-long-writing -a claude-code`. Or copy the skill folder (packages/core/skills/inkos-long-writing in Narcooo/inkos) into .claude/skills/inkos-long-writing in your project. Claude Code loads it when a task matches its description.
How do I install InkOS Long-Form Narrative Craft in Codex?
Run `npx skills add Narcooo/inkos --skill inkos-long-writing -a codex`. Or copy the skill folder (packages/core/skills/inkos-long-writing in Narcooo/inkos) into .agents/skills/inkos-long-writing in your project. Codex loads it when a task matches its description.
Can I use InkOS Long-Form Narrative Craft in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Narcooo/inkos --skill inkos-long-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inkos-long-writing, .gemini/skills/inkos-long-writing, .github/skills/inkos-long-writing and .opencode/skills/inkos-long-writing in your project.
What does InkOS Long-Form Narrative Craft need to run?
SKILL.md names no scripts, command-line tools or credentials: InkOS Long-Form Narrative Craft is instructions for the agent only.
Does InkOS Long-Form Narrative Craft access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is InkOS Long-Form Narrative Craft safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does InkOS Long-Form Narrative Craft use?
InkOS Long-Form Narrative Craft is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does InkOS Long-Form Narrative Craft use?
About 867 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to InkOS Long-Form Narrative Craft?
Skills that share tags, products or a category with InkOS Long-Form Narrative Craft: Chinese Novel Writing System (leenbj/novel-creator-skill, 671 stars), Chinese Novelist Chapter Writer (PenglongHuang/chinese-novelist-skill, 3.3k stars), Sun-Style Restrained Narrative Writing (KKKKhazix/sun-style-writing, 403 stars) and Short Web Fiction Writer (uu201/character-arc, 583 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains InkOS Long-Form Narrative Craft?
Narcooo (a GitHub user) maintains it in Narcooo/inkos, which has 10,226 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.
Source: Narcooo/inkos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.