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.
Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does.
Install Prose Critique
$ npx skills add BingHanOfUESTC/open_agent_team --skill prose-critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team prose-critique --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/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/teams/story_team/skills/prose-critique .claude/skills/prose-critique && 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 "prose-critique" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critique into .claude/skills/prose-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-critique", 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/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critiqueType 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 BingHanOfUESTC/open_agent_team --skill prose-critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team prose-critique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/teams/story_team/skills/prose-critique .agents/skills/prose-critique && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prose-critique" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critique into .agents/skills/prose-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-critique", 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 BingHanOfUESTC/open_agent_team --skill prose-critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team prose-critique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/teams/story_team/skills/prose-critique .cursor/skills/prose-critique && 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 "prose-critique" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critique into .cursor/skills/prose-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-critique", 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/BingHanOfUESTC/open_agent_team.git --path teams/story_team/skills/prose-critique--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 BingHanOfUESTC/open_agent_team --skill prose-critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team prose-critique --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/teams/story_team/skills/prose-critique .gemini/skills/prose-critique && 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 "prose-critique" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critique into .gemini/skills/prose-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-critique", 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 BingHanOfUESTC/open_agent_team prose-critiqueInstalls 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 BingHanOfUESTC/open_agent_team --skill prose-critique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .github/skills && cp -r skills-src/teams/story_team/skills/prose-critique .github/skills/prose-critique && 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 "prose-critique" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critique into .github/skills/prose-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-critique", 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 BingHanOfUESTC/open_agent_team --skill prose-critique -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team prose-critique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/teams/story_team/skills/prose-critique .opencode/skills/prose-critique && 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 "prose-critique" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/prose-critique into .opencode/skills/prose-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-critique", 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
prose-critique- GitHub stars
- 106
- Token cost
- ~1.5k tokens
- SKILL.md length
- 756 words
- Files
- 9
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does.
- Reviewing drafts
- SKILL.md covers Your Focus, What Makes a Good Finding, Communicating Impact and The Adversarial Mindset, plus 4 more sections
- Runs Python scripts from its folder; calls uv
- Evaluating prose quality
What it does
Prose Critique is an agent skill from BingHanOfUESTC/open_agent_team. Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `resources/analyze.py`, `resources/antipatterns.md` and `resources/baseline.md`).
It sits in Writing & Content, covering Creative writing and fiction. The repository describes itself as: Build persistent multi-agent teams that collaborate like real organizations to deliver complex tasks. The licence is MIT.
When your agent uses it
- Reviewing drafts
- Evaluating prose quality
- Assessing changes at any stage
Example prompts
- “/prose-critique”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 7e28736. 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
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
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
Prose Critique loads about 1.5k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 756 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 BingHanOfUESTC/open_agent_team at commit 7e28736, republished under its MIT licence (© BingHanOfUESTC). 756 words, ~1,474 tokens.
Download SKILL.mdSave it as
.claude/skills/prose-critique/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- prose-critique
- description
- Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
- type
- reference
- model-invocable
- false
Prose Critique
Find what doesn't work. The writer already believes their draft works: challenge that assumption. A critique that says "well done" without digging is worse than no critique, because it creates false confidence.
Your Focus
Your prompt specifies a focus area. Go deep on the assigned focus rather than skimming everything. Each focus area has a dedicated resource with detailed guidance:
resources/structure.md: plot logic, pacing, scene necessity, stakes, setup/payoffresources/character.md: motivation coherence, arc progression, relationship dynamicsresources/voice.md: dialogue quality, POV consistency, subtext, voice driftresources/prose.md: line-level quality, rhythm, clarity, repetition, show vs tellresources/continuity.md: facts, timeline, geography, character state
Read the relevant resource when assigned that focus. If no focus is specified, assess the draft yourself: figure out which dimensions matter most for this piece, read those resources, and focus there.
Even with an assigned focus, flag issues outside it if they're clearly serious. A voice reviewer who notices a plot hole should say so.
What Makes a Good Finding
Good findings share these qualities:
Specific. Reference the chapter, scene, paragraph, or line. "The pacing has issues" is not a finding.
Reasoned. Explain why it matters, not just that it exists. A POV break is only interesting if you can describe what it costs: reader trust, immersion, character distinction.
Directable. The writer should know what to do after reading your finding. If the fix isn't clear, say what investigation or decision is needed.
Non-obvious. Spell-check already caught the typos. You're here for things that require understanding context, intent, and interaction between story elements.
What wastes everyone's time
- Vague "this could be stronger" without explaining how or why
- Restating what the prose says without identifying a problem
- Praising things that work (unless specifically asked for balanced feedback)
- Findings about established story decisions the author already committed to: critique the execution, not the premise
Communicating Impact
Make it obvious which findings are serious and which are minor. The orchestrator or author triaging your findings has context you don't: they know what's intentional, what's set up for later, what's a known compromise. Give them a clear signal about severity.
Lead with the things that damage the reading experience: broken causation, character inconsistency, lost tension, confused POV. Let the smaller observations follow. Only flag issues you can tie to a concrete reader cost.
Show full SKILL.md (376 more words)Show less
The Adversarial Mindset
Think about how the prose fails, not how it succeeds:
- Motivation. Does this character have a reason to do what they're doing here? Would they actually say this?
- Causation. Does this scene follow logically from the previous one? Is the character's reaction earned by what happened?
- Tension. Is the conflict real? Are stakes at risk? Does the scene resolve too easily?
- POV discipline. Does the narrator know things they shouldn't? Are other characters' internal states reported as fact?
- Voice consistency. Does the narrator sound like the same person throughout? Do characters maintain their distinct voices?
- Reader experience. Where would a reader's attention drift? Where would they feel confused, cheated, or talked down to?
Don't be adversarial for its own sake. If a section is genuinely strong, you can note it briefly, but earn that conclusion by actually reading critically, not by wanting to be nice.
Calibrating to Stage
Early draft: focus on structural and character issues. Line-level prose quality doesn't matter if the scene shouldn't exist or the character motivation is broken.
Mid-stage draft: structural foundations should be solid. Focus on voice, pacing, and how scenes connect.
Late draft: structure and character are committed. Focus on prose quality, line-level rhythm, word choice, and polish.
Don't spend time on prose-level polish of a scene that has structural problems. Fix the bones before the skin.
Your Report
Open with a brief overall assessment: what's the big picture for this draft? Then walk through findings grouped by severity or by theme, whichever tells a clearer story. End with your verdict: what's the most important thing to address, and what's the one change that would improve this draft the most?
In multi-critic workflows (fan-out pattern), keep your report focused on your assigned area. The orchestrator synthesizes across critics: you go deep, not broad.
Optional: Mechanical Analysis
A bundled script measures mechanical prose properties: sentence length distribution, opener variety, dialogue ratio, repetition, pronoun distribution. These are quantitative signals useful for comparing a draft against the project's own baseline. Read-only agents (critic, continuity-checker) should request this data from the orchestrator; agents with bash access can run it directly:
uv run resources/analyze.py <file.md> [window_size]Resources
resources/antipatterns.md: AI writing antipatterns, categorized as research-backed vs community folkloreresources/baseline.md: establishing a project baseline and comparing drafts against it
© BingHanOfUESTC, MIT. 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 8 other files in teams/story_team/skills/prose-critique of BingHanOfUESTC/open_agent_team.
- SKILL.md
- resources/analyze.py
- resources/antipatterns.md
- resources/baseline.md
- resources/character.md
- resources/continuity.md
- resources/prose.md
- resources/structure.md
- resources/voice.md
Open the folder on GitHubat commit 7e28736
Compare with similar skills
Prose Critique 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 |
|---|---|---|---|---|---|---|
| Prose Critique this skillBingHanOfUESTC/open_agent_team | 106 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode | 7.4k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| InkOS Creative HarnessNarcooo/inkos | 10k | 1 repos | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Novel Arteternityspring/shuohao-skills | 4.3k | — | ~1.1k | Automated safety check: Notes | Apache-2.0 | |
| SepiaNanako0129/sepia | 3.1k | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Short Web Fiction Trend Scan
zenstory-ai/oh-story-claudecode
Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.
InkOS 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.
Novel Art
eternityspring/shuohao-skills
给 AI 短剧出美术设定集（场景 + 叙事道具）：场景的设计意图、一致性锚点、光照时段变体、 空景提示词；道具的戏剧功能、状态变体、尺度参照、白底无手提示词。
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
Story Toolbox Router
zenstory-ai/oh-story-claudecode
Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.
More from BingHanOfUESTC/open_agent_team
All 30 skills in this repoSkill Validation And Evaluation
BingHanOfUESTC/open_agent_team
A skill your agent uses when validating a newly created or updated agent skill with structure checks, routing positive and negative examples, contamination checks, progressive disclosure review, and…
Autoresearch Orchestration
BingHanOfUESTC/open_agent_team
A skill your agent uses when autoresearchteam needs to manage an end-to-end research lifecycle from Boss brief to literature, idea, implementation, experiments, synthesis, and LaTeX delivery.
Experiment Iteration Loop
BingHanOfUESTC/open_agent_team
A skill your agent uses when designing, running, logging, diagnosing, or iterating experiments for the selected research idea.
Latex Paper Artifact
BingHanOfUESTC/open_agent_team
A skill your agent uses when producing the final arXiv-style LaTeX paper, BibTeX, figures, tables, reproducibility statement, appendix, and artifact manifest.
Literature Evidence Mapping
BingHanOfUESTC/open_agent_team
A skill your agent uses when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
Media Asset Sourcing
BingHanOfUESTC/open_agent_team
A skill your agent uses when PPT slides need external images, screenshots, logos, product photos, stock-like visuals, diagrams, or videos that must be downloaded, inserted, or linked with source and…
Related
Categories
Questions about Prose Critique
What does Prose Critique do?
Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Prose Critique is an agent skill from BingHanOfUESTC/open_agent_team. Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does.
When should I use Prose Critique?
Prose Critique fits situations like: reviewing drafts; evaluating prose quality; assessing changes at any stage.
How do I install Prose Critique in Claude Code?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill prose-critique -a claude-code`. Or copy the skill folder (teams/story_team/skills/prose-critique in BingHanOfUESTC/open_agent_team) into .claude/skills/prose-critique in your project. Claude Code loads it when a task matches its description.
How do I install Prose Critique in Codex?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill prose-critique -a codex`. Or copy the skill folder (teams/story_team/skills/prose-critique in BingHanOfUESTC/open_agent_team) into .agents/skills/prose-critique in your project. Codex loads it when a task matches its description.
Can I use Prose Critique 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 BingHanOfUESTC/open_agent_team --skill prose-critique -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prose-critique, .gemini/skills/prose-critique, .github/skills/prose-critique and .opencode/skills/prose-critique in your project.
What does Prose Critique need to run?
Going by SKILL.md and its folder, Prose Critique needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Prose Critique access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Prose Critique 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 Prose Critique use?
Prose Critique is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prose Critique use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Prose Critique?
Skills that share tags, products or a category with Prose Critique: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Creative Harness (Narcooo/inkos, 10k stars) and Novel Art (eternityspring/shuohao-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prose Critique?
BingHanOfUESTC (a GitHub user) maintains it in BingHanOfUESTC/open_agent_team, which has 106 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on June 23, 2026.
Source: BingHanOfUESTC/open_agent_team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.