AugmentClaude
Docs

Prose Review

By naodeng· naodeng/awesome-qa-skills· 0

Review skill documentation for completeness, clarity, and technical accuracy.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/skill-prose-review-naodeng/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Use this skill when reviewing the contract completeness of Skills, Prompts, metadata, or QA documentation; triggers include Skill prose review, Prompt review, and contract audit.

What this skill does

Skill Prose Contract Review

When to use

  • Review a Skill, Prompt, metadata, example, or output format.
  • Check whether prose is executable, independently installable, and verifiable.

Workflow

  1. Confirm scope and document role.
  2. Trace trigger → input → rules → output → constraints → verification.
  3. Report blockers, important suggestions, location, impact, and evidence.
  4. List missing information and unverified claims.

Constraints

  • Do not invent behavior, tools, or facts.
  • Do not report static reading as runtime validation.
  • Do not rewrite files unless explicitly requested.

On-demand loading

  • Read prompts/skill-prose-review.md before producing the review.
  • Use evals/ for evaluation and report static and runtime evidence separately.

Final checklist

  • Scope and document role are explicit
  • Input, output, constraints, and verification are covered
  • Gaps and evidence levels are stated
  • No unauthorized file changes

Related skills

C

Claude API Helper

anthropics

Build, debug, and optimize Claude API applications with caching and model migration support.

OfficialComplete terms in LICENSE.txt
D

Documentation Co-Authoring

anthropics

Guide structured workflows for writing docs, proposals, and technical specs collaboratively.

Official
P

PPTX Text Extractor

axoviq-ai

Extract text and speaker notes from PowerPoint presentations.

AGPL-3.0-or-later
M

Memory Search

davila7

Search conversation history and recall previous discussions, decisions, and context.