Adversarial multi-view fiction review (full/lean/solo)
Review novel chapters across structure, characters, prose and setting with a 4-agent pipeline and severity-ranked S1–S4 findings — written in Chinese
- What
- Review novel chapters across structure, characters, prose and setting with a 4-agent pipeline and severity-ranked S1–S4 findings — written in Chinese
- Cost
- Free
- Needs
- a Claude Code / OpenCode / Codex / Antigravity / OpenClaw runtime able to spawn sub-agents (or solo mode); the oh-story-claudecode agents deployed in the project (run /story-setup first, otherwise the skill auto-degrades to solo); fiction chapters or outlines to review; an agent able to work in Chinese (the skill is written in Chinese)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @zenstory-ai's review coordinator from the `oh-story-claudecode` writing toolkit: an iron rule that review finds problems rather than validating correctness. `/story-review full` spawns 4 reviewer agents (story-architect, character-designer, narrative-writer, consistency-checker), `lean` spawns two, `solo` runs one — with automatic degradation (missing/malformed agents, spawn failures, runtime without sub-agent support) and an embedded fallback rubric pack when reference files are unreadable. Every reviewer emits findings in a unified S1–S4 schema (severity, category, location, evidence, issue, fix), reports are written for the author (must-fix / should-fix / can-skip, quoted evidence, reader-impact reasoning, no internal jargon), and a fixed technical-note line records the actual mode, fallback and rubric used. Honest caveats: **the skill is written in Chinese** (style resolution follows the Chinese copy-layout guide); targeted at web-fiction platforms (Fanqie, Qidian, Zhihu rubrics built in); `story-review` never edits prose, settings or outlines — it only reports; author-habit memory may explain intent but never lowers rubric severity. By @zenstory-ai, listed here with credit to its creator. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Claude Code / OpenCode / Codex / Antigravity / OpenClaw runtime able to spawn sub-agents (or solo mode); the oh-story-claudecode agents deployed in the project (run /story-setup first, otherwise the skill auto-degrades to solo); fiction chapters or outlines to review; an agent able to work in Chinese (the skill is written in Chinese) Install "Adversarial multi-view fiction review (full/lean/solo)" for me. It teaches an agent @zenstory-ai's story-review coordinator: run adversarial reviews in full (4 reviewer agents), lean (2) or solo mode with automatic degradation, emit findings in the unified S1–S4 schema (structure, character, prose, consistency, platform, factual, format, causal), apply the built-in web-fiction rubrics (Fanqie/Qidian/Zhihu) or an embedded fallback pack when references are unreadable, and write author-facing reports (must-fix/should-fix/can-skip with quoted evidence) plus the fixed technical-note line — review only, never edits prose. MIT-licensed. Repository: https://github.com/zenstory-ai/oh-story-claudecode/blob/main/skills/story-review/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "story-review". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run /story-setup in my fiction project to deploy the reviewer agents, then point the agent at the chapters to review). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.