Total 54,072 skills, Documentation & Writing has 1524 skills
Showing 12 of 1524 skills
Technical writer specializing in the Diátaxis documentation framework
Diagnose world-level story problems. Use when settings feel thin, institutions feel designed rather than evolved, economies don't make sense, or non-human species feel like humans in costume. Applies systemic worldbuilding principles to identify specific gaps and recommend interventions.
Transform AI-sounding text into natural, human-like writing by applying proven linguistic patterns and stylistic techniques. Use when text needs to sound more conversational, authentic, and less robotic - especially for essays, assignments, professional writing, blog posts, emails, or any content where human voice matters. Applies sentence variation, natural phrasing, contractions, personal voice, and removes AI tell-tale patterns.
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
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.
This skill should be used when the user asks to "prepare conference presentation", "create presentation slides", "design poster", "make academic poster", "write promotion content", "create Twitter thread", or mentions post-acceptance conference preparation. Provides comprehensive workflow for presentation, poster, and promotion content creation.
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Use when the user says "write an ADR", "document this decision", "record why we chose X", "add an architecture decision record", "create an ADR for", or wants to capture the reasoning behind a technical choice so the team understands it later. Do NOT use when the decision hasn't been made yet (use create-rfc instead), for implementation planning (use technical-design-doc-creator), or for general documentation.
Meta-skill for creating genre-analysis-based writing skills. Analyzes a corpus of article sections, discovers clusters, and generates complete skills with phases, cluster guides, and techniques.
This skill should be used when the user asks to "format markdown", "write markdown documentation", "follow markdown style guide", "apply markdown conventions", or needs guidance on markdown best practices.
Create structural blueprints for blog posts before writing. Analyzes topic briefs, selects structure templates, generates outlines with word counts and section summaries. Use when planning a new post, brainstorming structure, or deciding scope before drafting. Use for "outline", "plan post", "structure this topic", "how should I organize". Do NOT use for writing actual post content, editing existing posts, or SEO keyword planning.
Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report