Total 50,330 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Write blog posts/newsletters in YOUR voice with research and citations
Create organized, visual study notes with folder structures, diagrams, and example-based learning from source materials (PDFs, lecture notes, documentation). Use when creating structured learning materials, exam preparation notes, or educational documentation. Triggers - organize study notes, create visual learning materials, generate notes with diagrams, exam prep notes, example-based learning.
Use when implementing features, refactors, or fixes that affect core functionality, configuration, infrastructure, or integrations. Ensures documentation stays accurate by updating README, operational guides, and reference docs, and verifying links/commands remain correct.
Guidelines for creating and modifying markdown files. Use when writing documentation, README files, or any markdown content.
Use when generating, updating, or organizing documentation (component/API docs, project indexes, diagrams, tutorials, learning paths) - provides structured workflows and references for docs generation, indexing, diagrams, and teaching.
Full content production pipeline from blank page to publish-ready piece. Covers competitive research, content briefs, drafting, SEO optimization, readability scoring, editorial quality gates, and internal linking. Use when writing blog posts, articles, guides, or long-form content end-to-end, or when user mentions write a post, draft an article, create content, content pipeline, editorial workflow, content operations, content calendar management, repurposing, or content at scale.
Transform technical jargon into clear explanations using before/after comparisons, metaphors, and practical context
Create well-structured RFCs and technical proposals for software projects. Use this skill whenever the user wants to write an RFC, technical proposal, design doc, architecture doc, or system design overview. Also trigger when the user says things like "write an RFC", "I need to propose a new system", "create a technical proposal", "document the architecture", "write up the design", "I need a design doc", or "explain the system architecture in a doc". Even if they just say "RFC", "design doc", or "arch doc", use this skill. Covers both RFCs (proposing what to build) and architecture docs (documenting an existing codebase).
Generates monthly/quarterly investor updates. Takes KPIs, milestones, challenges, financials. Writes professional investor-update.md with highlights, metrics dashboard, product updates, team news, financial summary, upcoming milestones, asks. Multiple tones from seed-stage casual to Series B formal. Use when founders need to communicate progress to investors.
This skill should be used when a team wants to create or refine the technical guidelines document — for example "create the tech steering doc", "document our tech stack", "write the technical guidelines", "document our architecture decisions", "set up the tech steering", or "update the tech doc". Generates docs/steering/TECH.md as a living document capturing the stack, architecture patterns, constraints, commands, and ADRs. Generated once and refined — not regenerated from scratch.
Static site generators, documentation platforms, and deployment workflows for technical documentation
Produce implementation-ready specs from approved intent, repository context, and known constraints.