// 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.
Create or update OpenAPI specifications and API documentation for Apify endpoints. Use when user says "add API endpoint", "create OpenAPI spec", "document this endpoint", "add code samples for API", "update API docs", or "api-doc". Handles OpenAPI YAML, schemas, code samples, and operation IDs.
Write or edit Apify documentation pages following the style guide. Use when user says "write docs for", "create a new page", "document this feature", "add documentation about", "edit this doc page", or "write a guide for [topic]". Handles platform docs, guides, and reference pages with proper formatting and structure.
Create structured tutorials for Apify Academy or Platform documentation. Use when user says "create a tutorial", "write a tutorial", "build a step-by-step guide", "convert this guide into a tutorial", or "tutorial for [topic]". Handles tutorial structure, learning objectives, prerequisites, step-by-step instructions, code examples, and troubleshooting sections.
| name | review-docs |
| description | 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. |
| allowed-tools | Read Bash Glob Grep Agent |
| model | sonnet |
| argument-hint | file-path |
git status to confirm you have the latestpnpm lint:md (heading hierarchy, list numbering, spacing)vale "<file>" --minAlertLevel=error (prose style, pronouns, dashes, code fences, admonitions).agents/skills/review-docs/scripts/check-frontmatter.sh "<file>" (description char count)standards/writing-style.md (voice, tone, headings, links)standards/content-standards.md (front matter, admonitions, code blocks)standards/terminology.md (product names, article usage)standards/grammar-rules.md (hyphenation, punctuation, brand spelling)
Launch all 4 in parallel..agents/skills/review-docs/references/review-format.mdDeterministic 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.