Review a document through specialized lenses using parallel agents. Use when reviewing documentation, blog posts, READMEs, proposals, or any prose for quality issues across content, style, and embedded artifacts.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add bendrucker/claude --skill review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bendrucker-review-46390987)More formats (shields.io, HTML) on the badges page.
---
name: writing:review
description: |
Review a document through specialized lenses using parallel agents. Use when reviewing documentation, blog posts, READMEs, proposals, or any prose for quality issues across content, style, and embedded artifacts.
argument-hint: "<doc-path> [--lens content|style|artifacts]"
context: fork
agent: general-purpose
allowed-tools:
- Read
- Grep
- Glob
- Task
- WebFetch
---
# Document Review
Review a document through parallel agents, each covering a different lens.
## Inputs
$ARGUMENTS
The first positional is the document path. If none is provided, ask the user. Optionally accept target audience and focus areas.
- `--lens content|style|artifacts`: run only the named lenses. Comma-separate to select more than one (`--lens content,style`). Default: all applicable lenses per [Dispatch Agents](#dispatch-agents).
## Dispatch Agents
Read the document. Always spawn `writing:content` and `writing:style`. Spawn `writing:artifacts` only if the document contains URLs, markdown links, Mermaid code blocks, or markdown tables.
When `--lens` is set, restrict the dispatch to the named lenses. `artifacts` still spawns only when the document actually contains links, diagrams, or tables.
Spawn all applicable agents in parallel. Each receives the document content, audience, and focus areas.
## Synthesize
Merge agent findings into one report. Deduplicate (keep the more detailed description), group by severity (Blocking > Important > Suggestions) rather than by agent, and order by document position within each severity. Each finding carries its section reference, issue, suggested fix, and which agent(s) flagged it.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!