Agent Skills › Narcooo/inkos › inkos-long-writing

inkos-long-writing

GitHub

提供长篇小说创作的专业叙事技巧,涵盖场景构建、人物因果、信息释放节奏及连载结构。指导AI在写作、审查和修订阶段遵循具体规范,确保情节连贯、角色动机合理及文本质量。

packages/core/skills/inkos-long-writing/SKILL.md Narcooo/inkos

Trigger Scenarios

用户请求创作长篇小说或章节 需要对小说内容进行场景重构或情节优化 执行小说文本的审查、修订或润色任务

Install

npx skills add Narcooo/inkos --skill inkos-long-writing -g -y
More Options

Non-standard path

npx skills add https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-long-writing -g -y

Use without installing

npx skills use Narcooo/inkos@inkos-long-writing

指定 Agent (Claude Code)

npx skills add Narcooo/inkos --skill inkos-long-writing -a claude-code -g -y

安装 repo 全部 skill

npx skills add Narcooo/inkos --all -g -y

预览 repo 内 skill

npx skills add Narcooo/inkos --list

SKILL.md

Frontmatter
{
    "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.

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.

Version History

  • 8fc2ae5 Current 2026-09-27 10:49

    完成 InkOS 2.0 创意工作流和恢复契约的更新,补充了关于基础构建中因果线连接、卷末状态及角色代价的具体指导内容。

  • 0910483 2026-09-08 17:31

Same Skill Collection

packages/core/skills/inkos-interactive-film/SKILL.md
packages/core/skills/inkos-long-market-research/SKILL.md
packages/core/skills/inkos-long-story-analysis/SKILL.md
packages/core/skills/inkos-play-world/SKILL.md
packages/core/skills/inkos-script-writing/SKILL.md
packages/core/skills/inkos-short-market-research/SKILL.md
packages/core/skills/inkos-short-story-analysis/SKILL.md
packages/core/skills/inkos-short-writing/SKILL.md
packages/core/skills/inkos-story-cover/SKILL.md
packages/core/skills/inkos-story-deslop/SKILL.md
packages/core/skills/inkos-story-import/SKILL.md
packages/core/skills/inkos-story-review/SKILL.md
packages/core/skills/inkos-storyboard/SKILL.md
packages/core/skills/inkos-translation/SKILL.md
skills/SKILL.md
packages/core/skills/inkos-continuation-writing/SKILL.md
packages/core/skills/inkos-fanfic-writing/SKILL.md
packages/core/skills/inkos-imitation-writing/SKILL.md
packages/core/skills/inkos-play-illustration/SKILL.md
packages/core/skills/inkos-spinoff-writing/SKILL.md

Metadata

Files
0
Version
8fc2ae5
Hash
8d881f59
Indexed
2026-09-08 17:31

ホーム - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-09-29 18:47
浙ICP备14020137号-1