Story Multi-Perspective Review
zenstory-ai/oh-story-claudecode
Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.
Reviews chapters or manuscripts against the standard that fits their genre, audience and your own criteria, showing concrete issues and revising only when asked.
Install InkOS Story Review
$ npx skills add Narcooo/inkos --skill inkos-story-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Narcooo/inkos inkos-story-review --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-story-review .claude/skills/inkos-story-review && 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-story-review" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-story-review into .claude/skills/inkos-story-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-story-review", 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-story-reviewType 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-story-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Narcooo/inkos inkos-story-review --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-story-review .agents/skills/inkos-story-review && 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-story-review" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-story-review into .agents/skills/inkos-story-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-story-review", 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-story-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Narcooo/inkos inkos-story-review --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-story-review .cursor/skills/inkos-story-review && 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-story-review" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-story-review into .cursor/skills/inkos-story-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-story-review", 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-story-review--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-story-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Narcooo/inkos inkos-story-review --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-story-review .gemini/skills/inkos-story-review && 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-story-review" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-story-review into .gemini/skills/inkos-story-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-story-review", 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-story-reviewInstalls 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-story-review -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-story-review .github/skills/inkos-story-review && 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-story-review" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-story-review into .github/skills/inkos-story-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-story-review", 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-story-review -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-story-review --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-story-review .opencode/skills/inkos-story-review && 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-story-review" agent skill from https://github.com/Narcooo/inkos/tree/master/packages/core/skills/inkos-story-review into .opencode/skills/inkos-story-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inkos-story-review", 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-story-review- GitHub stars
- 10k
- Token cost
- ~450 tokens
- SKILL.md length
- 230 words
- Files
- 2 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Reviews chapters or manuscripts against the standard that fits their genre, audience and your own criteria, showing concrete issues and revising only when asked.
- Reviewing a novel chapter against its genre and audience
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Getting concrete, evidence-backed issues instead of a vague score
- Checking a long-running serial for stalled plot or repeated beats
What it does
The agent first identifies the applicable standard from genre, target audience, tone, platform and your stated preferences, since comedy, literary fiction, romance, mystery and commercial serials should not share one threshold for logic density. In an active book it audits saved chapters and reports each issue with severity, evidence and likely reader impact. A parser or model-format failure is reported as review unavailable, never as proof the prose is bad.
For long-form work it compares a chapter with memo requirements, recent progression, hook ids, character knowledge and promises made to readers, and treats repetition as non-progress. Repairs are routed by cause: local prose defects can be patched, while missing scenes, broken causality, timeline, viewpoint or payoff problems need structural revision. Revision happens on request, keeps your voice, targets the smallest scope and reports whether the change was applied. A review matrix reference is loaded for full reviews or disputed standards.
When your agent uses it
- Reviewing a novel chapter against its genre and audience
- Getting concrete, evidence-backed issues instead of a vague score
- Checking a long-running serial for stalled plot or repeated beats
- Revising only the passages that have a real defect
Example prompts
- “Review chapter twelve of my mystery draft for pacing and clue fairness.”
- “This is a web-serial romance for young adult readers; judge it by that standard, not as literary fiction.”
- “Fix only the broken timeline in chapter three and leave my voice alone.”
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 Story Review loads about 450 tokens when it runs, and up to ~997 if it reads all its reference files. Until then it costs about 28 tokens; SKILL.md has 230 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). 230 words, ~450 tokens.
Download SKILL.mdSave it as
.claude/skills/inkos-story-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- inkos-story-review
- description
- 按题材、目标读者和用户标准审稿，展示具体问题并协作修订。Use for chapter or manuscript review with transparent criteria.
Story review
Use this skill when the user wants diagnosis, comparison, review, or revision advice for existing prose.
- First identify the applicable standard from genre, target audience, tone, platform, and explicit user preference. Everyday comedy, literary fiction, romance, mystery, and commercial serials should not share one logic-density threshold.
- In an active book, use the auditor for persisted chapters. Show concrete issue descriptions, severity, evidence, and likely reader impact.
- A parser or model-format failure produces a review-unavailable observation. It is not evidence that the prose is bad and never authorizes a rewrite.
- Revise when the user asks or an explicit production action requests revision; report whether the revised artifact was actually applied.
- Preserve the user's voice and successful passages. Prefer the smallest scope that resolves the real defect.
- For long-form work, compare the chapter with populated memo requirements, recent progression, real hook ids, character knowledge, and reader promises. Repetition is not progression; a payoff, subplot, or emotional line moves only when facts, action, relationship, status, or understanding changes.
- Route repairs by cause: local prose defects may be patched, while missing scenes, broken causality, timeline, viewpoint, character logic, or payoff require structural revision.
- Respond in the user's language.
Load references/review-matrix.md for a full review or when standards are disputed. The matrix is qualitative guidance, not a scorecard. For spinoffs, use parent canon as authority; for fanfic, honor fanficMode and explicit allowed deviations.
© 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 1 other file (references) in packages/core/skills/inkos-story-review of Narcooo/inkos.
- SKILL.md
- references/review-matrix.md
Open the folder on GitHubat commit 8fc2ae5
Compare with similar skills
InkOS Story Review 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 Story Review this skillNarcooo/inkos | 10k | — | ~450 | Automated safety check: Pass | AGPL-3.0 | |
| Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Web Novel AI-Trace Removerzenstory-ai/oh-story-claudecode | 7.4k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Web Novel AI-Flavor Removeruu201/character-arc | 583 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Character Managementdanjdewhurst/story-skills | 286 | 1 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Web Novel Polishing and De-AIuu201/character-arc | 583 | 1 repos | ~508 | Automated safety check: Pass | MIT |
Similar skills
Web Novel AI-Trace Remover
zenstory-ai/oh-story-claudecode
Rewrites AI-sounding Chinese web novel text so it reads naturally, changing as little as possible and keeping plot, names and numbers intact.
Web Novel AI-Flavor Remover
uu201/character-arc
Finds and rewrites AI-sounding passages in Chinese web novel text, changing as few words as possible while keeping plot, characters and names intact.
Character Management
danjdewhurst/story-skills
This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character relationships", "character timeline", "character…
Web Novel Polishing and De-AI
uu201/character-arc
Polishes AI-generated web novel text to remove machine-sounding patterns, with rewriting strategies, instruction templates, style techniques and before-and-after examples.
Editorial Review
danjdewhurst/story-skills
This skill should be used when the user asks for a "sensitivity reader", "authenticity reader", "cultural review", "is this portrayal okay", "real people in my novel", "defamation", "can I use song…
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.
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.
InkOS Story Import
Narcooo/inkos
Imports an existing novel manuscript into an InkOS project, rebuilds its story state, and keeps your own chapters apart from reference material and fan-fiction canon.
Related
Categories
Questions about InkOS Story Review
What does InkOS Story Review do?
Reviews chapters or manuscripts against the standard that fits their genre, audience and your own criteria, showing concrete issues and revising only when asked. The agent first identifies the applicable standard from genre, target audience, tone, platform and your stated preferences, since comedy, literary fiction, romance, mystery and commercial serials should not share one threshold for logic density. In an active book it audits saved chapters and reports each issue with severity, evidence and likely reader impact.
When should I use InkOS Story Review?
InkOS Story Review fits situations like: reviewing a novel chapter against its genre and audience; getting concrete, evidence-backed issues instead of a vague score; checking a long-running serial for stalled plot or repeated beats; revising only the passages that have a real defect.
How do I install InkOS Story Review in Claude Code?
Run `npx skills add Narcooo/inkos --skill inkos-story-review -a claude-code`. Or copy the skill folder (packages/core/skills/inkos-story-review in Narcooo/inkos) into .claude/skills/inkos-story-review in your project. Claude Code loads it when a task matches its description.
How do I install InkOS Story Review in Codex?
Run `npx skills add Narcooo/inkos --skill inkos-story-review -a codex`. Or copy the skill folder (packages/core/skills/inkos-story-review in Narcooo/inkos) into .agents/skills/inkos-story-review in your project. Codex loads it when a task matches its description.
Can I use InkOS Story Review 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-story-review -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-story-review, .gemini/skills/inkos-story-review, .github/skills/inkos-story-review and .opencode/skills/inkos-story-review in your project.
What does InkOS Story Review need to run?
SKILL.md names no scripts, command-line tools or credentials: InkOS Story Review is instructions for the agent only.
Does InkOS Story Review 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 Story Review 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 Story Review use?
InkOS Story Review 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 Story Review use?
About 450 tokens (SKILL.md is roughly 1.8k 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 547 tokens, read only when the agent opens those files.
What are the alternatives to InkOS Story Review?
Skills that share tags, products or a category with InkOS Story Review: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Web Novel AI-Trace Remover (zenstory-ai/oh-story-claudecode, 7.4k stars), Web Novel AI-Flavor Remover (uu201/character-arc, 583 stars) and Character Management (danjdewhurst/story-skills, 286 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains InkOS Story Review?
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.