Skip to content
Back to skills

Inkos Long Writing

ASecurity

长篇小说的场景构造、人物因果、信息释放与连载节奏。Used by InkOS long-form workers as their shared craft method.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
businessgoreact

Works with

  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add Wanfeng1028/muse --skill inkos-long-writing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Inkos Long Writing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Inkos Long Writing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wanfeng1028-inkos-long-writing/badge)](https://www.skillsdirectory.com/skills/wanfeng1028-inkos-long-writing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Files in this skill

  • SKILL.md3.4 KB
  • references/foundation-design.md2.1 KB
  • references/reader-contract-and-progression.md2.7 KB
  • references/scene-dialogue-and-length-budget.md1 KB
  • references/state-projection.md2.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.