skills/authors-critique/SKILL.md
Get a fast, cheap gut-check critique of a draft from multiple author personas. Usage - /authors-critique <file> [author1 author2 ...]. Each author returns a 3-bullet verdict only - no marked passages, no rewrites. Defaults to 3 authors if none specified. Use when you want quick directional feedback before investing in a full /authors-edit pass.
npx skillsauth add sethshoultes/great-authors-plugin authors-critiqueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fast, cheap gut-check critique.
/authors-edit with — use critique to triage.Not for: marked-up passages (that's /authors-edit); craft debates between two authors (that's /authors-debate).
Parse arguments: file path (required) + optional author names. Same parsing as /authors-edit.
Verify the file exists.
If no authors named, pick 3 using the same genre-signal logic as /authors-edit, but with a wider net. Default triad: Hemingway + Orwell + Didion for ambiguous cases (covers sentence-level, argument clarity, observational specificity).
Fan out via Agent tool. Dispatch all authors in parallel in a single message. For each:
subagent_type: <author>-personamodel: "haiku" (override — critique is opinion-style and tolerates the cheaper model; edit and debate stay on Sonnet)CRITIQUE MODE - TERSE OUTPUT ONLY.
Read this draft and respond with EXACTLY 3 bullets. Each bullet is one sentence. No introduction. No markdown markup of passages. No rewrites. Just the three most important things you notice.
End with one line: "If I'm not the right voice here, try <X>." — or omit if you are.
Draft:
<full file contents>
Consolidate:
# /authors-critique on <filename> — <author A>, <author B>, <author C>
## <Author A>
- <bullet 1>
- <bullet 2>
- <bullet 3>
## <Author B>
- <bullet 1>
- <bullet 2>
- <bullet 3>
## <Author C>
- <bullet 1>
- <bullet 2>
- <bullet 3>
## Consensus
(one sentence naming what all or most authors flagged)
## Sharpest disagreement
(one sentence naming the most productive disagreement, or "no significant disagreement" if so)
## Handoffs
(if any author suggested a different voice, name them here)
Output to stdout. No manuscript changes.
model: "haiku" as an override. This is intentional — critique is opinion-style work that doesn't require Sonnet-level reasoning. If you find critiques losing quality on Haiku (e.g., personas drift off-voice, cross-references hallucinate), drop the override in the Agent call and the dispatch falls back to the agent's default model: sonnet.documentation
Dispatch a named author persona as a sub-agent to rewrite an existing manuscript file from scratch with full bible context. Usage - /authors-rewrite <file> <author>. Use when an existing chapter or scene needs more than a critique pass — when the prose itself isn't working and a clean rewrite by the named author is required. The skill assembles a self-contained brief (bible files, prior/next chapters, architecture beats, voice rules), dispatches the author, and confirms save.
tools
Top-level autonomous workflow for writing a novel end-to-end with the great-authors plugin. Composes existing skills (project-init, build-character, build-place, build-relationship, draft, channel, rewrite, continuity, critique, edit, debate, journal, consolidate) into a multi-phase pipeline with human checkpoints. The human provides direction (premise, genre, characters, voice); the AI orchestrator dispatches author personas as sub-agents to do the work. Use when a user wants the full great-authors pipeline run for them with minimal hand-holding — analogous to great-minds-plugin's agency-* workflows. Usage - /authors-orchestrate-novel, optionally with --phase <N> to run a single phase or --resume to continue from the last checkpoint.
data-ai
Run ONE editor across MULTIPLE files in parallel, then consolidate into a corpus-level pattern report. Surfaces patterns no per-file critique catches — voice drift, recurring tics, structural failures that only become visible across multiple pieces. Usage - /authors-corpus-critique <author> <path-or-glob> [<path-or-glob>...]. Different from /authors-critique (N authors on 1 file). This is 1 author on N files.
tools
Initialize the per-project memory bible (.great-authors/) in the current working directory. Creates project.md, voice.md, timeline.md, glossary.md, and empty characters/, places/, scenes/ directories. Use when the user is starting a new writing project (novel, essay collection, long-form nonfiction) and wants author personas to have persistent context across sessions.