Docs & Writing

involvex Skill

API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.

involvex Skill

Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices

8421bit Bundle

Documents business processes with Mermaid flowcharts. Use for process documentation, workflow design, or system analysis.

valentinnikolaev Bundle

Review code changes and report evidence-backed defects, actionable test gaps, and verification limits without editing. Use for uncommitted changes, path-filtered diffs, or pull-request diffs; use plan-review for implementation plans and fix-pr for GitHub review-comment remediation.

valentinnikolaev Bundle

Create or improve usable command-line and console commands or apps, including Laravel Artisan, Symfony Console, and similar frameworks. Use for command structure, signatures, help, prompts, progress, errors, output, machine formats, automation behavior, and implementation-ready CLI UX. Do not use for web, mobile, native GUI, shell scripting without UX changes, terminal themes, full-screen TUIs, or report-only audits.

valentinnikolaev Bundle

Remove or shorten redundant source-code comments without changing behavior. Use for explicit comment cleanup or dry audits of user-specified files and directories; do not use for general refactoring, documentation generation, or generated-output cleanup.

l4ci Bundle

Use when the user wants to diagnose a team's stage of development and what it needs to advance, or asks why a team is stuck, conflicted, or not yet performing. Fans out five parallel assessor subagents (one per stage: Forming, Storming, Norming, Performing, Adjourning), each scoring how well the team's observable behaviors match that stage with evidence and noting regression signals, then synthesizes the current stage, the matching leadership focus, the concrete moves to advance, and what is blocking the transition into a detailed markdown report. Triggers include "Tuckman", "stages of team development", "forming storming norming performing", "what stage is my team at", "why is my team stuck".

l4ci Bundle

Use when the user wants to attack a goal or problem backward instead of forward, asking what would guarantee failure or the opposite outcome so those paths can be avoided. Fans out parallel subagents that each generate ways to cause the worst result across a distinct lens, then ranks the failure paths, distills the absolute bright lines, and turns each into an avoid-rule or action in a markdown report. Triggers include "inversion", "invert the problem", "work backward", "how could this fail", "avoid stupidity", "Munger inversion".

l4ci Bundle

Use when the user wants to assess organizational alignment or effectiveness, diagnose why an organization underperforms, plan a major change, or integrate after a merger, using the McKinsey 7-S framework (Strategy, Structure, Systems, Shared Values, Skills, Style, Staff). Fans out seven parallel analyst subagents (one per element), then runs an alignment analysis across them to find misalignments and recommend fixes, in a detailed markdown report. Triggers include "7-S", "7S framework", "McKinsey 7-S", "organizational alignment", "why is this org not working".

l4ci Bundle

Use when the user wants a SWOT analysis of a company, product, project, team, or decision, or asks to assess strengths, weaknesses, opportunities, and threats. Fans out four parallel analyst subagents (one per quadrant), grounds each factor in evidence and prioritizes it, then crosses the quadrants into a TOWS strategy matrix and a ranked set of strategic options in a detailed markdown report. Triggers include "SWOT", "SWOT analysis", "strengths and weaknesses", "TOWS", "analyze our position".

l4ci Bundle

Use when the user wants a VRIO analysis of a firm's resources and capabilities, or asks whether a resource is a source of sustained competitive advantage. Optionally surfaces candidate resources first, then fans out one analyst subagent per resource to run the four VRIO gates (Valuable, Rare, Costly to Imitate, Organized) with evidence and assign a competitive implication, then synthesizes the strategic core and fixable gaps into a detailed markdown report. Triggers include "VRIO", "VRIN", "resource-based view", "is this a sustainable advantage", "test our core competencies", "RBV".

l4ci Bundle

Use when the user wants to understand why customers hire a product, shape or reposition an offering around real customer motivation, or decide what to build based on the progress customers are trying to make. Defines the customer and the struggling moment, then fans out parallel analyst subagents over the functional job, the emotional and social job, the desired outcomes, the competing solutions and nonconsumption, and the four forces of progress, and synthesizes a job story, an opportunity-scored ranking of outcomes, and implications for the offering into a detailed markdown report. Triggers include "jobs to be done", "JTBD", "what job is the customer hiring this for", "why do customers switch", "outcome-driven innovation".

cedws Bundle

Generate a Terragrunt dispatcher and missing version-specific skills from official Terragrunt releases and documentation. Use when seeding or refreshing this repository with stable Terragrunt minor releases from the last three years.

carlheath Bundle

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

carlheath Bundle

Academic work with scientific rigor — covers literature search, source evaluation, and writing. Configurable language. [WHAT] End-to-end support: (1) systematic literature search and source evaluation, (2) thematic synthesis, (3) writing essays, papers, reports, dissertations, literature reviews, method discussions. IMRAD structure, Harvard/APA, peer review. [WHEN] Use when: academic, scientific, essay, report, dissertation, literature review, paper, thesis, doctoral, peer-reviewed, systematic review, find sources, zotero, Harvard reference, APA, IMRAD, source criticism, literature review, research synthesis. NOT for: opponent role (academic-opponent), interview coding (gioia-analysis). [LANGUAGE] Configurable. Matches input. [EXPERTISE] Academic writing, IMRAD, source criticism, systematic literature search, Harvard/APA citations, thematic synthesis, qualitative/quantitative methods.

carlheath Skill

Web scraping skill with a 4-tier strategy: WebFetch (fast, static), searxng (search-driven), BrightData scrape_as_markdown (anti-bot, JS-rendered), Playwright (interactive, login-required). Picks the right tool per target URL. [WHAT] Scraping for OSINT, intelligence monitoring, source verification. Default: start cheapest (WebFetch), escalate as needed. BrightData for Cloudflare / anti-bot-protected sites. Playwright for login or heavy SPAs. [WHEN] Use when: scrape, fetch URL, crawl, extract content, read site, capture article, mirror page, extract markdown, anti-bot. NOT for: web search (use searxng or exa), archiving (use Wayback). [LANGUAGE] English and other languages. Output content matches source language.

carlheath Skill

Create read-aloud scripts for teleprompter. Plain prose without headings or bullet lists, calibrated for reading time at a natural reading speed. [WHAT] READ-ALOUD SCRIPT — text optimised to be spoken. Format: continuous prose, natural breathing pauses, short to medium sentences, no headings, no bullets. Length calibrated to target time at ~150 words/min as default. [WHEN] Use when: teleprompter script, voiceover script, video script, podcast script, "script for X minutes", read-aloud manuscript, YouTube script. NOT for: cue cards (use talking-points), slides (use presentation), op-ed (use op-ed). [LANGUAGE] Configurable. Output: plain prose ready to read directly. [EXPERTISE] Teleprompter writing, oral rhythm (~150 wpm), natural breathing pauses, scene-building without visual structure, word-counting for length calibration.

carlheath Skill

After finished text work, identify concepts, people, places, and ideas worth atomic notes (Cards), link in existing cards, and suggest updates to cards where the new material casts new light on already-established ideas. [WHAT] Scan recently produced/edited text against `Cards/_index.md`. Return three lists: NEW CANDIDATES (concepts worth their own card), EXISTING TO LINK IN (cards that exist but aren't linked), EXISTING TO UPDATE (cards where the text adds something substantive). The user chooses per row. Closes "the loop" between writing and the knowledge graph. [WHEN] Use when: atomize, "suggest atomic notes", "link in cards", "update cards", after a finished chronicle/memo/report, after the ALGORITHM VERIFY phase on text-producing work. Use PROACTIVELY as a silent last step in the Algorithm's VERIFY phase when produced text is >800 words. [LANGUAGE] Configurable. Output: short, scannable list. No AI filler patterns. [EXPERTISE] Atomic notes, Zettelkasten weave, concept extraction, Cards index lookup, wiki

carlheath Skill

Weekly dual-memory flow: review project auto-memory (inbox) and promote to global memory, keep as ephemeral, or delete. Addresses the dual-memory tension in a layered memory system. [VAD] Structured walkthrough of `~/.claude/projects/.../memory/`. Classifies each entry as promote/keep/delete based on type and stability. Writes promotions to global memory. Writes a review report. [WHEN] Use when: promote memory, dual-memory, weekly memory review, memory promotion, review project memory, "is this memory stable?", "should this go global?", inbox cleanup of memory. [LANGUAGE] Configurable. [EXPERTISE] Memory architecture, ephemeral-vs-persistent classification, three-criteria evaluation (recurrence, generality, stability).

carlheath Skill

Create talking points and cue cards for radio, TV interviews, panel debates, and oral appearances. Format: core message first, one-liners, bridging for hard questions. [WHAT] ORAL DELIVERY — optimised to be SAID. Core messages first, one-liners with depth, bridging for hard questions, counter-argument handling, imagery. Cue cards, not finished text. [WHEN] Use when: talking points, radio interview, TV interview, media interview, panel debate, speech, dinner speech, opening speech, "prepare interview", "before TV", "before radio", "cue cards", "interview prep". NOT for: slides (use presentation), read-aloud script (use teleprompter), written debate (use op-ed). [LANGUAGE] Configurable. [EXPERTISE] Oral communication, broadcast media, rhetoric, bridging, message discipline. [DISTINCTION] chronicle = written chronicle | op-ed = written argumentation | presentation = slide flow | talking-points = CUE CARDS for ORAL interview/panel

carlheath Skill

Umbrella skill for reading a text artefact (chronicle, memo, report, transcript) and extracting candidates to the Ogmios KNOWLEDGE area in one operation. Classifies into 7 entity types: People, Organizations, Places, Events, Concepts, Sources, Research. The user chooses per candidate: create KNOWLEDGE node / archive to vault / skip / save in _inbox. [WHAT] Complement to atomize-zettel (Cards/Zettelkasten in vault). Atomize works against vault Cards/, extract-entities works against the Ogmios KNOWLEDGE area. [WHEN] Use when: extract entities, identify people/organizations/places, who is mentioned in this text, mining from text to KNOWLEDGE. [LANGUAGE] Configurable. [EXPERTISE] Entity extraction, NER classification, KNOWLEDGE-area routing.

carlheath Bundle

Technical Writing Specialist - Clear, comprehensive technical documentation. [VAD] README files, API documentation, tutorials, user guides, architecture docs. OpenAPI/Swagger specifications, Markdown, Docusaurus, MkDocs. [NÄR] Use when: README, documentation, API docs, tutorial, guide, installation, user manual, help docs, code documentation, changelog, release notes [EXPERTISE] Developer docs, user guides, API specs, progressive disclosure

carlheath Bundle

Knowledge Management Specialist - Personal knowledge systems, note-taking, information organization. [VAD] PKM systems design, Zettelkasten methodology, atomic notes, MOCs. Linking strategies, knowledge graphs, documentation structure. [NÄR] Use when: knowledge management, PKM, notes, Obsidian, Zettelkasten, atomic notes, MOC, knowledge base, documentation, wiki, second brain, note-taking [EXPERTISE] PKM, Obsidian, atomic notes, linking strategies, knowledge graphs

carlheath Skill

Integration, narrative, and final production for intelligence analysis. [WHAT] Weaves together SIGNAL, STRUCTURE, and CONTEXT into coherent, decision-relevant products. Creates briefs, situation reports, scenarios. [WHEN] Use when: analysis brief, situation report, scenario, strategic summary, final product, communicate to decision-makers. [EXPERTISE] Narrative integration, synthesis, decision-relevant communication, scenario writing. Core principle: complexity should become graspable without being oversimplified.

danielleit241 Bundle

Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis.

danielleit241 Skill

Write technical journal entries analyzing recent changes. Use for session reflections, change analysis, decision documentation.

danielleit241 Bundle

Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.

danielleit241 Bundle

Create, edit, analyze .docx Word documents. Use for document creation, tracked changes, comments, formatting preservation, text extraction, template modification.

danielleit241 Bundle

Create, edit, analyze .pptx PowerPoint files. Use for presentations, slides, layouts, speaker notes, template modification, content extraction, slide generation.

brandonburrus Bundle

This skill should be used when implementing any feature, fixing any bug, or changing any code behavior, before writing the implementation code. It also applies when the user says "TDD", "test first", "red-green-refactor", "write the test before the code", when authoring automated end-to-end browser tests (Playwright) for a user journey, and after the fix skill has reproduced a bug's root cause, to write the regression test first. It should not be used to diagnose a reported bug (use fix; it hands off here), for pure configuration changes, documentation, static content, or for runtime-verifying an already-built change (use the verify skill for that).

brandonburrus Skill

This skill should be used when generating or organizing a documentation set for a codebase, library, CLI, or API: writing a README and docs from scratch, filling documentation gaps, or restructuring docs that have become a confusing pile. It applies when the user says "document this", "write the docs", "the docs are a mess", "add docs for this feature", or "what docs does this need". It should not be used for the prose craft of a single explainer or tutorial (use teach-through-writing), for recording one architectural decision (use spec), or for API contract definition (use spec).

brandonburrus Bundle

This skill should be used when creating, editing, or reading Microsoft Word documents (.docx), including text, headings, styles, tables, images, and headers or footers. It applies when the user says "create a Word doc", "update this docx", "read the Word document", "fill in this template", or references a .docx file. It should not be used for Markdown or plain-text writing (write directly), for PDFs (use edit-pdf), or for legacy .doc files without converting them to .docx first.

brandonburrus Skill

This skill should be used when writing persuasive technical documents (spikes, proposals, RFCs, or vendor evaluations) where the goal is to convince stakeholders to adopt a recommended approach. It applies when the user says "write a proposal", "make the case for", "pitch this", "convince the team to", "write an RFC to adopt X", or "spike writeup"; this is the persuade-to-adopt RFC, whereas a design RFC that specifies how to build is the spec skill. It should not be used for pure documentation, reference material, or educational content where the goal is reader understanding rather than persuasion, for recording a decision already made (use spec), or for the staged migration plan itself (use spec; this skill writes the pitch that gets it adopted).

brandonburrus Bundle

This skill should be used when drafting, editing, or writing blog posts for blog.brandonburrus.com. It should not be used for Confluence docs, READMEs, internal technical writing, or any writing not destined for the blog.

brandonburrus Bundle

This skill should be used when writing or formatting Markdown files for an Obsidian vault. It applies when the user mentions Obsidian, vault, wikilinks, or Obsidian-flavored Markdown, or when a .obsidian directory is detected. It should not be used for GitHub READMEs, static site generators, or any Markdown renderer that is not Obsidian.

brandonburrus Bundle

This skill should be used when creating, editing, or reading PowerPoint presentations (.pptx), including slides, layouts, placeholders, text, images, tables, charts, speaker notes, and click-to-reveal builds and animations. It applies when the user says "make a slide deck", "create a presentation", "update these slides", "add a slide", "reveal the bullets one at a time", or references a .pptx file. It should not be used for diagrams as standalone artifacts (use create-diagram), for visual design direction of non-slide UIs (use design), or for legacy .ppt files without converting to .pptx first.