New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Docs Reviewer

by strands-agents in strands-agents/box

Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink).

Apache-2.0Auto-check passedDevelopment

Install Docs Reviewer

skills CLI
$ npx skills add strands-agents/box --skill docs-reviewer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install strands-agents/box docs-reviewer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/strands-agents/box.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docs-reviewer .claude/skills/docs-reviewer && rm -rf skills-src

Use ~/.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/

Facts

Skill name
docs-reviewer
GitHub stars
249
Token cost
~1.3k tokens
SKILL.md length
719 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink).

  • Works in 6 steps: Placement and shape → Altitude → Readability → …
  • Tasks that involve Plain language and style rules
  • SKILL.md covers Procedure, Dimensions, Verdicts and Output format, plus 1 more section
  • Runs Shell scripts from its folder

What it does

Docs Reviewer is an agent skill from strands-agents/box. Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink). Use after docs-writer produces a draft, before a docs pull request, or when asked to "review this draft", "check my docs", or "is this page ready to ship". Read-only.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `check-prose.sh`).

It sits in Development, covering Plain language and style rules and Pull requests. The repository describes itself as: Run AI agents in a sandbox that restricts what they can execute, read, write, and reach on the network. Box combines OS isolation with default-deny Dogwood policies and… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Plain language and style rules
  • Tasks that involve Pull requests

Example prompts

  • “review this draft”
  • “check my docs”
  • “is this page ready to ship”
  • “/docs-reviewer”

Requirements

  • A Bash shell

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Placement and shape
  2. Altitude
  3. Readability
  4. Constraints and terminology
  5. Claim scope
  6. Examples, diagrams, and standing alone

What it can do on your machine

Read from SKILL.md and the folder at commit 331d563. 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 (Shell), which the agent can run.

    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

Docs Reviewer loads about 1.3k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 719 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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 strands-agents/box at commit 331d563, republished under its Apache-2.0 licence (© strands-agents). 719 words, ~1,348 tokens.

Download SKILL.mdSave it as .claude/skills/docs-reviewer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
docs-reviewer
description
Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink). Use after docs-writer produces a draft, before a docs pull request, or when asked to "review this draft", "check my docs", or "is this page ready to ship". Read-only.

Documentation reviewer

Scope. Whether a draft is in the right place, shaped around its subject, at the right altitude, easy to read, and consistent with the terminology lock, measured against voice-guide.md. You don't check that a claim is correct against the code and its tests. That's the docs-audit skill.

Readability and altitude come first. A page can pass every mechanical rule and still be a page nobody wants to read, and that's a fail.

Procedure

  1. Read the draft once straight through, as its reader would. Note where you had to reread.

  2. Run the mechanical check, and use its hits as input to dimension 4:

    sh
    .agents/skills/docs-reviewer/check-prose.sh <draft>

  3. Classify the content type from the directory and the structure.

  4. Score each dimension below as pass, warning, or fail.

  5. Give one verdict.

  6. Write the review in the output format.

Dimensions

1. Placement and shape
  • The page is in the right guide. A user page that argues a design, or a design page that's a list of options, is in the wrong guide.
  • The structure follows the subject. A page about several parts has one section per part, and no part is spread across sections. A page about one task follows the reader's order.
  • No section mixes content types. Conceptual background in a how-to guide is a finding.
  • No section exists only to fill a template slot.
  • The page doesn't do the job of decisions.md, terminology.md, or tenets.md.
2. Altitude
  • Each detail belongs to this page. Detail that belongs to a sibling topic (a wire protocol on a page about binaries, Seatbelt rules on a page about policy) is a finding, even when that page doesn't exist yet.
  • Length fits the subject. A draft that's much longer than the subject needs is a finding.
3. Readability
  • Read aloud, each sentence sounds like a person said it. Quote each one that doesn't, and give a plainer version.
  • Each section opens with what the reader needs first. A design section says what the thing is before what it guarantees.
  • A list isn't walked through twice.
  • Each term is introduced before its shorthand is used.
4. Constraints and terminology
  • The words not to use, em-dashes, emoji, padded triads, and negative parallelism. Apply the override table for the content type.
  • User guide: describe what is, and no "why" unless it changes the action.
  • Each word from the "do not use" column of docs/design/terminology.md is a finding. A term the lock doesn't have, or a lock term that the code calls something else, is a question for the user.
Show full SKILL.md (296 more words)Show less
5. Claim scope
  • Each reason links its decision anchor the first time it comes up, and the decision is summarized, not copied. A reason with no link is a finding.
  • A claim stated more broadly than the mechanism it describes is a finding.
  • No test name, no source file, no issue or pull request number, no file.rs:LINE citation, and no link into .agents/drafts/ or .agents/explorations/.
6. Examples, diagrams, and standing alone
  • Each example is complete and realistic, one concept per block, with the output below the command.
  • Prose and code agree.
  • Each diagram shows the main path only, is Mermaid with every label quoted, and has no ASCII art.
  • The first paragraph says what the page covers. Prerequisites are stated, terms are defined or linked on first use, and no cross-reference carries the load.

Verdicts

Ship it. All dimensions pass, with one minor warning at most.

Tighten. Two or more warnings, or one fail that an edit in place fixes. Typical causes: a few sentences that don't read aloud, detail that belongs on another page, terminology slips, or a draft much longer than it needs to be. Give a fix for each finding, at its line.

Rethink. Two or more fails, or one structural fail: the wrong guide, a shape that spreads each part across sections, a page mostly at the wrong altitude, or prose that reads like a spec throughout. Give the diagnosis and the right approach.

If you can't decide between Tighten and Rethink, ask: can the writer fix this in place, or do they need to re-outline? In place is Tighten. Re-outline is Rethink.

Output format

markdown
## Review: <page title>

**Guide and type:** <user guide or design guide>, <type>
**Verdict:** Ship it | Tighten | Rethink

| Dimension | Score | Key finding |
|---|---|---|
| Placement and shape | ... | ... |
| Altitude | ... | ... |
| Readability | ... | ... |
| Constraints and terminology | ... | ... |
| Claim scope | ... | ... |
| Examples, diagrams, standing alone | ... | ... |

### Findings

1. <file>:<line>: <the finding>. Fix: <the fix>.

### What works

<Two or three things the draft does right.>

What this skill doesn't do

  • Edit the draft. The writer fixes it.
  • Check a claim against the code. That's docs-audit.
  • Commit, push, or approve a pull request.

© strands-agents, Apache-2.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 in .agents/skills/docs-reviewer of strands-agents/box.

  • SKILL.md
  • check-prose.sh

Open the folder on GitHubat commit 331d563

Compare with similar skills

Docs Reviewer 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.

Docs Reviewer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Reviewer this skillstrands-agents/box249—~1.3kAutomated safety check: PassApache-2.0
Issue BriefVasiHemanth/tokentelemetry377—~1.5kAutomated safety check: PassMIT
Explain This PRVarnan-Tech/opendirectory674—~1.2kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins10k10 repos~2.4kAutomated safety check: PassNone
Cap Feature Building WorkflowCapSoftware/Cap23k—~2.5kAutomated safety check: WarnCustom licence
Docs Reader Reviewprisma/web1.1k—~2.4kAutomated safety check: PassNone

Similar skills

  • Issue Brief

    VasiHemanth/tokentelemetry

    Explain a GitHub issue, discussion, or feature request in plain language before deciding whether to build it.

    377 GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Explain This PR

    Varnan-Tech/opendirectory

    Takes a GitHub PR URL or the current branch and writes a plain-English explanation of what it does and why, then posts it as a PR comment.

    674 GitHub stars~1.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed

  • Cap Feature Building Workflow

    CapSoftware/Cap

    Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: warnings

  • Docs Reader Review

    prisma/web

    Official

    A skill your agent uses when a docs page or section has been written or rewritten and is about to be handed over, when the operator says "reader review", "does this read like a human wrote it", "too…

    1.1k GitHub stars~2.4k tokensUpdated today
    Writing & ContentAuto-check passed

  • Code Review

    hardness1020/Leeway

    Code quality review — identify patterns, anti-patterns, and improvements.

    116 GitHub stars~301 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

More from strands-agents/box

All 10 skills in this repo

  • Authoring Box Policy

    strands-agents/box

    Author or edit a Strands Box policy (policy.dw) — turn an operator's natural-language allow/deny intent into a validated Dogwood policy over the box's fixed action vocabulary, including when…

    249 GitHub stars~5.4k tokensUpdated today
    Auto-check passed

  • Debug Os Failure On GitHub

    strands-agents/box

    Debug a CI failure on an OS you are not on (you are on Linux, it fails on macos-latest, or the reverse) without opening a pull request per attempt.

    249 GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Docs Planner

    strands-agents/box

    Find the gaps in the Box documentation and produce a prioritized backlog for docs/user/ and docs/design/.

    249 GitHub stars~743 tokensUpdated today
    Auto-check passed

  • Docs Writer

    strands-agents/box

    Draft or rewrite a Box documentation page in docs/user/ (tutorial, how-to, or reference for an operator) or docs/design/ (explanation for a security evaluator or a contributor), or a crate README.md…

    249 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Kd

    strands-agents/box

    Deep-dive a SINGLE key decision. An agent skill from strands-agents/box.

    249 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Spec

    strands-agents/box

    Walk through spec-driven development, design then requirements, producing a local .spec.md and .requirements.md for one feature.

    249 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Docs Reviewer

What does Docs Reviewer do?

Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink). Docs Reviewer is an agent skill from strands-agents/box. Review a Box documentation draft in docs/user/ or docs/design/ for placement, structure, altitude, readability, terminology, and claim scope, and give a verdict (Ship it, Tighten, or Rethink).

When should I use Docs Reviewer?

Docs Reviewer fits situations like: tasks that involve Plain language and style rules; tasks that involve Pull requests.

How do I install Docs Reviewer in Claude Code?

Run `npx skills add strands-agents/box --skill docs-reviewer -a claude-code`. Or copy the skill folder (.agents/skills/docs-reviewer in strands-agents/box) into .claude/skills/docs-reviewer in your project. Claude Code loads it when a task matches its description.

How do I install Docs Reviewer in Codex?

Run `npx skills add strands-agents/box --skill docs-reviewer -a codex`. Or copy the skill folder (.agents/skills/docs-reviewer in strands-agents/box) into .agents/skills/docs-reviewer in your project. Codex loads it when a task matches its description.

Can I use Docs Reviewer 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 strands-agents/box --skill docs-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-reviewer, .gemini/skills/docs-reviewer, .github/skills/docs-reviewer and .opencode/skills/docs-reviewer in your project.

What does Docs Reviewer need to run?

Going by SKILL.md and its folder, Docs Reviewer needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Docs Reviewer 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 Docs Reviewer 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 Docs Reviewer use?

Docs Reviewer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docs Reviewer use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Docs Reviewer?

Skills that share tags, products or a category with Docs Reviewer: Issue Brief (VasiHemanth/tokentelemetry, 377 stars), Explain This PR (Varnan-Tech/opendirectory, 674 stars), Technical Writing Standard (cursor/plugins, 10k stars) and Cap Feature Building Workflow (CapSoftware/Cap, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Reviewer?

strands-agents (a GitHub organization) maintains it in strands-agents/box, which has 249 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.

Source: strands-agents/box on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.