mcpbeat

Doc Write

apify/doc-write

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.

1k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
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 doc-write

What comes with it

4 237 bytes besides the instruction
references/doc-structures.md
references/process.md

The instruction itself

2 sections, as written by the author

Documentation writing

Process

  • Determine doc type - platform docs, guide, or reference (tutorials → use /tutorial)
  • Research - read related existing pages, check standards/terminology.md for product names
  • Create front matter - title (sentence case), description (140-160 chars), sidebar_position, slug
  • Write content following the structure for the doc type:
  • Platform docs: intro → prerequisites → main content → code examples → next steps
  • Guides: intro with goal → step-by-step instructions → verification → troubleshooting
  • Reference: brief description → parameters/options → examples → related pages
  • Quality check - run pnpm lint:md and vale before finishing

Key rules: US English, active voice, imperative tone, sentence case headings, bold for UI elements only, all admonitions need titles, code blocks need language tags.

For detailed structure templates, see .agents/skills/doc-write/references/doc-structures.md.

For edge cases and process notes, see .agents/skills/doc-write/references/process.md.

How to use it

Copy the folder

Take apify/doc-write 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.