Total 53,693 skills, Documentation & Writing has 1514 skills
Showing 12 of 1514 skills
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.
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"
You are updating this project's CLAUDE.md to reflect **meta learnings** (conventions, philosophy, gotchas) and **significant recent changes** to the codebase.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
Эксперт по интеграционным спецификациям. Используй для документирования интеграций, webhooks, event schemas и data flows.
Write LinkedIn posts matching a specific technical author's voice — direct, analytical, dry-humored, and precise. Use this skill whenever the user asks to write, draft, rewrite, review, improve, or refine a LinkedIn post, social media post, tech commentary, or any public-facing short-form writing about technology, AI, software engineering, or developer tools. Also trigger when the user says "write this in my style", "post about this", "rewrite this for LinkedIn", "draft a post in my style", "does this sound right", "how should I phrase this", or provides raw content/notes and wants it shaped into a post. Includes visual companion guidance for pairing posts with document carousels (via md-to-pdf with Mermaid diagrams), custom images (via concept-to-image), or animations (via concept-to-video).
Generate Substack Note ideas by scanning published YouTube videos, newsletters, and Notes. Use when the user says 'generate note ideas', 'what should I post on Notes', 'note ideas from my content', 'mine my videos for Notes', or wants to maintain a consistent Notes posting cadence.
American business English writing style for professional communications. Direct, action-oriented, EN-US spelling. Use when writing emails, chat messages, proposals, client communications, or any business writing for American SME audiences. Applies to drafting, editing, and tone-checking any professional text.
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.
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.
Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments, create figure sketches, set a writing timeline, or write a pre-emptive rejection letter for planning purposes. Do NOT use for actual writing (use paper-writing), running experiments (use experiment-pipeline), self-reviewing a finished draft (use paper-review), or finding research problems (use research-ideation).
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice", "reframe style", or asks to apply the content style spec. Do NOT use for general writing tasks.