Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

$pwd:

review-docs

Name: Review Docs
Author: apify

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

Exécuter dans Manus

$ git log --oneline --stat

stars:69

forks:199

updated:5 mai 2026 à 12:37

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

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

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)
- vale "<file>" --minAlertLevel=error (prose style, pronouns, dashes, code fences, admonitions)
- .agents/skills/review-docs/scripts/check-frontmatter.sh "<file>" (description char count)
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.

related-skills.json

même dépôt

api-doc.md

from "apify/apify-docs"

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.

2026-05-0569

doc-write.md

from "apify/apify-docs"

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.

2026-05-0569

tutorial.md

from "apify/apify-docs"

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.

2026-05-0569

package.json

"author": "apify"

"repository": "apify/apify-docs"

Ouvrir le dépôt GitHub Voir les dépôts du créateur

$ install --global

$ download --local

Exécuter dans Manus

$ useful --forSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

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

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)
- vale "<file>" --minAlertLevel=error (prose style, pronouns, dashes, code fences, admonitions)
- .agents/skills/review-docs/scripts/check-frontmatter.sh "<file>" (description char count)
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.

review-docs

Documentation review

Process

Plus depuis ce dépôt

Documentation review

Process

Plus depuis ce dépôt