aidenlx/zotlit / .agents/skills/docs-writing
docs-writing
VerifiedPlan and produce ZotLit's reader-facing docs: lessons at /learn, recipes, answer pages and reference pages at /docs, landing copy. Use when adding, rewriting, moving or retitling a docs page, writing a fact sheet or writer brief, or checking a draft's labels, anchors and search title.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| references/brief/answer.opening.md | markdown | 358 B |
| references/brief/answer.shape.md | markdown | 1.8 KB |
| references/brief/lesson.opening.md | markdown | 348 B |
| references/brief/lesson.shape.md | markdown | 1.4 KB |
| references/brief/recipe.opening.md | markdown | 344 B |
| references/brief/recipe.shape.md | markdown | 2.0 KB |
| references/brief/shared.md | markdown | 3.2 KB |
| references/fact-sheet-model.md | markdown | 4.9 KB |
references/brief/lesson.shape.md
View on GitHub## The shape of a lesson
A step is short enough to hold in the head while looking at another window:
about 40 words of caption, one action, then the one thing the reader sees
when it worked. A lesson has the steps the fact sheet lists, in that order.
- **Cover:** the lesson title, one sentence on what the reader will have at
the end, and what they need before they start.
- **Each step:** a short title; the caption (the action, naming the control
by its on-screen label); the check (what they see when it worked, stated as
a fact about their screen); and the fixes the fact sheet lists for that
step, each as the thing the reader sees followed by what to do.
- **End:** one sentence on what they now have, and the next lesson.
The lesson title is one plain statement of the task, at most 60 characters,
in the words a researcher types into a search engine; the fact sheet lists
those words, and one of its phrasings is enough. The description is one
sentence, at most 160 characters.
The facts come from the fact sheet alone: every label, every result, every
fix, every example the reader types. Where the fact sheet is silent, leave
it out.
## What to return
Markdown, in this order: title, description, cover, then each step under a
`## Step N` heading with the parts `Title`, `Caption`, `Check`, `Fixes`, and
`Figure request` where you ask for one, then the end.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |