Total 50,391 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
Comprehensive editing checklist and procedures covering grammar and style rules, fact-checking, consistency verification, and readability metrics. Use when reviewing drafts, ensuring quality, or preparing content for publication.
Master the art of converting source material into authentic, human-written content. Transform transcripts, notes, and research into polished prose that avoids AI tells while maintaining distinctive voice. Combines anti-AI writing fundamentals with voice style adaptation.
Convert a taxonomy (`outline/taxonomy.yml`) into a bullet-only outline (`outline/outline.yml`) with sections/subsections. **Trigger**: outline builder, bullet outline, outline.yml, 大纲生成, bullets-only. **Use when**: structure 阶段（NO PROSE），已有 taxonomy，需要生成可映射/可写作的章节与小节骨架（每小节≥3 bullets）。 **Skip if**: 已经有批准过且可映射的 outline（避免无意义 churn）。 **Network**: none. **Guardrail**: bullets-only；移除 TODO/模板语句；每小节至少 3 个可检查 bullets。
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
Edits, rewrites, or improves text for clarity, tone, grammar, or style.
Transform technical jargon into clear explanations using before/after comparisons, metaphors, and practical context
Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.
Apply case study research design (Yin) to investigate how and why questions within real-life contexts using single or multiple case designs and triangulation. Use this skill when the user needs to choose between single and multiple case designs, apply holistic versus embedded units of analysis, triangulate evidence from multiple sources, or when they ask 'how should I structure a case study', 'single or multiple cases', or 'how do I ensure validity in case research'.
Analyzes a company's content to extract and codify their brand voice into a comprehensive style guide. Reads website copy, blog posts, emails, and social media to identify tone, vocabulary patterns, sentence structure, personality traits, and word preferences. Generates a brand-voice-guide.md and reviews new content against it.
Harness Engineering Phase 1 Step 2: Conduct in-depth analysis of project code and fill in the substantive content of each file in the docs/ knowledge base. Use this skill after the directory skeleton is created by harness-step1-create-agents-md. Immediately trigger this skill when the user says "fill document content", "improve docs/ files", "add substantive content to documents", "analyze project and write architecture document", "write ARCHITECTURE.md", or "write technical decision document". Prerequisite: The project already has AGENTS.md and the docs/ directory skeleton (created by harness-step1).
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.