How do I install the Review Docs skill?

Run npx skillmds@latest add apify/review-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review Docs?

apify (@apify) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review Docs by apify — Agent Skill

Name: Review Docs
Author: 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.

apify 14668ba 4 files · 9.0 KB Updated Sep 17, 2026

File contents

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.

---name: review-docsdescription: 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.---# Documentation review## Process1. **Verify file version** - `git status` to confirm you have the latest2. **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.3. **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.4. **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)5. **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`.

Frequently asked questions