Total 30,627 skills, Documentation & Writing has 1022 skills
Showing 12 of 1022 skills
Use this skill when writing, reviewing, or improving internal engineering documents - RFCs, design docs, post-mortems, runbooks, and knowledge base articles. Triggers on drafting a design proposal, writing an RFC, creating a post-mortem after an incident, building an operational runbook, organizing team knowledge, or improving existing documentation for clarity and completeness.
Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Handles business awards (Telstra, chamber of commerce), industry awards, and grant applications. Use when preparing any competitive submission where you need to demonstrate merit against defined criteria.
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION.
Use this skill when designing SDKs, writing onboarding flows, creating changelogs, or authoring migration guides. Triggers on developer experience (DX), API ergonomics, SDK design, getting-started guides, quickstart documentation, breaking change communication, version migration, upgrade paths, developer portals, and developer advocacy. Covers the full DX lifecycle from first impression to long-term retention.
Creative writing skill for analyzing and critiquing story content. Use when the user requests feedback, critique, or analysis of their writing. Provides balanced feedback calibrated to intended audience.
Generate an ARCHITECTURE.md file for a codebase following matklad's principles. Use when asked to "write an architecture doc", "create ARCHITECTURE.md", "document the architecture", "explain the codebase structure", "write a codemap", or when onboarding contributors to a project. Based on https://matklad.github.io/2021/02/06/ARCHITECTURE.md.html and modeled after rust-analyzer's architecture doc.
Document a Python module and its classes using Google style
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.
Write cold emails that actually get responses. Covers investors, employers, mentors, partners — anyone you don't know yet. Strict 2-4 sentence formula with real examples that got replies from Evan Spiegel, Mark Cuban, and Elon Musk. Triggers on requests like "cold email", "write an email to...", "reach out to...", "email this investor", "email this founder", "outreach email", "networking email", or any request to contact someone you don't have a relationship with yet.
Generate stories about institutional outcasts given impossible mandates with minimal resources. Use when you want team dynamics in hostile institutions, David vs. Goliath within organizations, or narrative tension from constraint-driven creativity.
Write stories designed to help listeners fall asleep. Use for bedtime podcasts, meditation content, calming narratives, or any content where the goal is gentle cognitive engagement that fades naturally into rest.
Create fables that embody paradoxical wisdom without resolving into simple morals. Use when exploring tensions that can't be resolved, when you need narrative forms that bypass analytical defenses, or when creating teaching stories.