Total 43,743 skills, Documentation & Writing has 1292 skills
Showing 12 of 1292 skills
Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** Feature skills, API documentation, existing code examples, or user-provided specifications. **Output type:** A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section.
Draft a long-form book review from your Reader highlights — synthesizing the book with your broader reading history to generate original arguments
Create release notes that summarize features, fixes, and migration guidance for software releases.
You must use this when producing any research prose — literature reviews, syntheses, analyses, methodology descriptions, discussion sections, abstracts, or any written output intended for an academic audience.
Create handoff documentation from One Horizon task data including completed/planned tasks, initiatives, and blockers. Use when asked to "write handoff notes", "prepare transition docs", or "document my current ownership". Requires One Horizon MCP.
Capture your Voice — the tone, rhythm, and rules that make your writing sound like YOU. This is the first element of the World Code framework. Use when someone says "define my voice", "writing voice", "tone of voice", "how I write", "voice element", or "capture my voice".
Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.
Write and maintain an implementation diary capturing what changed, why, what worked, what failed (with exact errors and commands), what was tricky, and how to review and validate. Activates proactively during non-trivial implementation work (new features, bug fixes, refactors, research spikes). Does not activate for trivial tasks like one-line fixes, config tweaks, or quick questions.
Creates new Architecture Decision Record (ADR) documents for significant architectural changes using a consistent template and repository-aware naming and storage guidance. Use when a user or agent decides on an architectural change, needs to document technical rationale, or wants to add a new ADR to the project history.
Rewrite "abstract conclusions from the author's perspective" into "specific pain point entrances from the reader's perspective", to avoid articles being too broad and empty, concept-first, and causing readers to swipe away. Suitable for WeChat Official Account articles, long-form articles, AI/platform/cognition/workplace/creator-oriented articles.
Use idiomatic doc comments to provide a professional API surface.
Use when the user needs research methodology, long-form content creation, academic-style citations, fact-checking, or evidence-based writing with proper source attribution. Trigger conditions: whitepaper drafting, research article writing, source evaluation, citation management, fact-checking protocol, case study creation, evidence-based argumentation.