Total 30,671 skills, Documentation & Writing has 1023 skills
Showing 12 of 1023 skills
Guide for creating effective internal technical documentation (READMEs, ADRs, Contribution Guides). Use this skill when the user asks to write, refactor, or improve internal project documentation.
Write Threads posts. Use when asked to write, create, draft, or produce a Threads post or Threads content. Also use when user mentions Threads in a social media writing context. Outputs short casual quick-take posts.
Activates the Technical Writer to generate, update, or refactor internal project documentation. Use when creating READMEs, ADRs, or technical guides.
This skill should be used when writing, modifying, or reorganizing documentation in docs/learned/. Use when creating new documents, updating frontmatter, choosing categories, creating index files, updating routing tables, or moving files between categories. Essential for maintaining consistent documentation structure.
Bind addressable evidence IDs from `papers/evidence_bank.jsonl` to each subsection (H3), producing `outline/evidence_bindings.jsonl`. **Trigger**: evidence binder, evidence plan, section->evidence mapping, 证据绑定, evidence_id. **Use when**: `papers/evidence_bank.jsonl` exists and you want writer/auditor to use section-scoped evidence items (WebWeaver-style memory bank). **Skip if**: you are not doing evidence-first section-by-section writing. **Network**: none. **Guardrail**: NO PROSE; do not invent evidence; only select from the existing evidence bank.
Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
Turn research findings into presentation outlines with narrative arc, data visualization suggestions, audience adaptation, and slide design guidance. Use when creating research presentations, conference talks, or findings briefings.
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers: brain/ modifications, "add to brain".
A skill for creating note articles in the interview format of kimny × Claude (AI). It defines release judgment rules based on quality gates (discovery, external anchor, one-sentence test), AIO optimization specifications, and dialogue format rules. Usage scenarios: (1) Creation and rewrite of note articles (2) Structuring interview-style articles (3) Converting historical conversations into articles (4) Article quality check. Example triggers: "I want to turn this into an article", "I want to write on note", "Use interview format", "Can this be made into an article?", "Rewrite the article", "Pass the quality gate", "AIO optimization", "note article"
Best practices for validating Dart documentation comments. Covers using `dart doc` to catch unresolved references and macros.