mcpbeat

Review Docs

apify/review-docs

Review Apify documentation for style guide compliance, quality standards, and best practices. Use when user says "review this doc", "check this page", "audit documentation", "review before PR", "is this ready to publish", or "review-docs". Runs automated checks and manual review against Apify style guide.

2k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
74
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/apify/apify-docs --skill review-docs

What comes with it

6 858 bytes besides the instruction
references/process.md
references/review-format.md
scripts/check-frontmatter.sh

What it tells the agent to use

found in the instruction text
Task spawns other agents

The instruction itself

2 sections, as written by the author

Documentation review

Process

  • Verify file version - git status to confirm you have the latest
  • Run deterministic checks (main process) - these are objective, no judgment needed:
  • pnpm lint:md (heading hierarchy, list numbering, spacing)
  • .agents/skills/review-docs/scripts/check-frontmatter.sh "<file>" (description char count)

Vale runs separately as a repo-level PR check and via the TW's local editor extension - don't invoke it here. The delegated standards review (step 3) covers the same prose-style ground.

  • Delegated standards review - spawn one subagent per standards file to check compliance. Each subagent reads the file being reviewed plus one standards file, and returns violations with line numbers and suggested fixes:
  • Subagent 1: check against standards/writing-style.md (voice, tone, headings, links)
  • Subagent 2: check against standards/content-standards.md (front matter, admonitions, code blocks)
  • Subagent 3: check against standards/terminology.md (product names, article usage)
  • Subagent 4: check against standards/grammar-rules.md (hyphenation, punctuation, brand spelling)

Launch all 4 in parallel.

  • Content review (main process) - focus on what standards files don't cover:
  • Content structure (clear intro, logical flow, next steps)
  • Technical accuracy (code examples correct, API endpoints current)
  • Completeness (prerequisites listed, edge cases covered)
  • Code example quality (complete, runnable, commented where needed)
  • Format output - merge subagent findings + deterministic results + content review per .agents/skills/review-docs/references/review-format.md

Deterministic tools first, then delegated standards checks, then content review. Report tool failures as objective facts. Report standards and content findings as judgment calls.

For detailed process notes and edge cases, see .agents/skills/review-docs/references/process.md.

How to use it

Copy the folder

Take apify/review-docs from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.