Total 53,577 skills, Documentation & Writing has 1512 skills
Showing 12 of 1512 skills
Interview-driven blog post drafting for technical product audiences. Use when user wants to write a blog post, article, or essay and needs help developing their thesis, structure, and initial draft. Triggers on "write a blog post", "draft an article", "help me write about X", "blog drafter", or when user has a topic they want to turn into written content. Conducts structured interviews using AskUserQuestion to extract the user's unique insights before generating drafts.
This skill should be used when the user asks to "write a book", "create book content", "book chapters", "book manuscript", "MVB", "authority book", or mentions writing a book from scratch. Creates complete book manuscripts from concept to final chapters.
Analyzes events through poetic lens using close reading, metaphor analysis, imagery, rhythm, form analysis, and attention to language's emotional and aesthetic dimensions. Provides insights on emotional truth, symbolic meaning, human experience, aesthetic impact, and expressive depth. Use when: Understanding emotional dimensions, symbolic meaning, communication impact, cultural resonance, human experience. Evaluates: Imagery, metaphor, rhythm, emotional truth, symbolic depth, aesthetic power, resonance, ambiguity.
Search, summarize, and synthesize economics literature
Write a systematic review protocol into `output/PROTOCOL.md` (databases, queries, inclusion/exclusion, time window, extraction fields). **Trigger**: protocol, PRISMA, systematic review, inclusion/exclusion, 检索式, 纳入排除. **Use when**: systematic review pipeline 的起点（C1），需要先锁定 protocol 再开始 screening/extraction。 **Skip if**: 不是做 systematic review（或 protocol 已经锁定且不允许修改）。 **Network**: none. **Guardrail**: protocol 必须包含可执行的检索与筛选规则；需要 HUMAN 签字后才能进入 screening。
Create and maintain technical documents, API documents, code comments, and project documents. Use this when you need to generate, update, or improve documentation.
Create Atomic Requirements (REQ) - Layer 7 artifact using REQ v3.0 format with 12 sections, SPEC-readiness scoring, and IMPL-readiness scoring
Guidelines for writing Rust documentation
Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
Guidelines for Go documentation including doc comments, package docs, godoc formatting, runnable examples, and signal boosting. Use when writing or reviewing documentation for Go packages, types, functions, or methods.
Governance-focused README with fixed structure and output contract. Use for asset governance, audit, or standardized first-impression docs. For process-driven creation (templates by project type) use crafting-effective-readmes.