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

inkos-short-writing

GitHub

用于生成完整商业短篇故事,涵盖构思、写作、审改及封面包装。支持用户定制前提与结构,强调因果逻辑与场景完整性,确保产出符合移动端阅读习惯的商业级作品。

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

Trigger Scenarios

需要创作独立商业短篇小说 请求对短篇故事进行整体审改或包装

Install

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

Non-standard path

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

Use without installing

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

指定 Agent (Claude Code)

npx skills add Narcooo/inkos --skill inkos-short-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-short-writing",
    "description": "商业短篇的构思、一次写完、整篇审改与包装。Use for confirmed standalone short-fiction production."
}

Short-fiction writing

Use this skill when the user wants a complete standalone commercial short story, not a long serial or a discussion-only answer.

  • Preserve the user's premise, emotional target, taboo, viewpoint, and ending preference. Ask only for a missing choice that would materially change the story.
  • User-specified chapter count and length are authoritative. When the user leaves them open, 12–18 focused chapters is a useful commercial default, not a production requirement or refusal boundary.
  • Apply the writing method to the operation authorized by the user and host.
  • Build one main line and at most one supporting reversal line. Prefer complete scenes over a synopsis montage at any requested scale.
  • Express personality and values through action. Every scene must move conflict, causality, evidence, emotion, payoff, or relationship.
  • Set up reversals and rewards through visible evidence; do not use sudden stupidity or unexplained luck.
  • Make decisive evidence causally credible through established access, motivation and actions. Dramatize its acquisition when a conflict or reversal depends on it; routine handling can use concise transitions. A delayed revelation may explain earlier possession without contradicting the established facts.
  • A discovery changes what the character knows. Later chapters must carry that knowledge forward instead of presenting the same identification as a new discovery. Likewise, a payment or other payoff already delivered must not arrive for the first time again later.
  • When a chapter is below its requested length, expand the missing confrontation, resistance, decision, evidence acquisition or emotional consequence into a complete scene. Do not meet length by repeating conclusions or reciting administrative steps.
  • Treat title, chapter titles, opening, full manuscript, synopsis, selling points, and cover direction as one coherent product.
  • Make the opening a concrete first-screen disturbance rather than an abstract pitch. Chapter titles promise the active pressure or turn; later chapters must not collapse into result summaries.
  • Keep mobile prose dense but breathable. Stage major reversals, confrontations, reveals, and payoffs beat by beat through action, dialogue, evidence, and sensory detail.
  • During revision, preserve the causal events and ending transition unless the user explicitly requests changes to them. Shorten by merging repeated reaction, explanation, and transition; lengthen with missing dramatic action rather than padding.
  • Packaging must describe the manuscript that actually exists. A cover direction serves a mobile portrait book cover with a readable title zone, strong emotion, recognizable story props, and the story's real conflict.
  • For a commercial mobile short-fiction cover, use a 3:4 portrait composition, a large two-to-four-line title zone, a close or half-body character with a charged expression, and only a few immediately recognizable conflict props. Favor high-contrast thumbnail readability over cinematic, corporate, magazine, or landscape-video aesthetics. When image-model lettering is unreliable, reserve a clean deterministic typography zone instead of asking for long generated text.
  • Report partial failures honestly; a cover failure must not erase a successful manuscript.
  • Respond in the user's language.

Load references/production-checklist.md before a full production run or whole-story revision.

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-long-writing/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-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
c199b94a
Indexed
2026-09-08 17:31

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