Claude Skills

This skill should be used when the user asks to "design multi-agent system", "implement supervisor pattern", "create swarm architecture", "coordinate multiple agents", or mentions multi-agent patterns, context isolation, agent handoffs, sub-agents, or parallel agent execution.

This skill should be used when the user asks to "start an LLM project", "design batch pipeline", "evaluate task-model fit", "structure agent project", or mentions pipeline architecture, agent-assisted development, cost estimation, or choosing between LLM and traditional approaches.

This skill should be used when the user asks to "design agent tools", "create tool descriptions", "reduce tool complexity", "implement MCP tools", or mentions tool consolidation, architectural reduction, tool naming conventions, or agent-tool interfaces.

Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.

Worker-Agent integration for intelligent task dispatch and performance tracking

Linear's proven methodology for software development and project organization. Use when helping users plan work, create issues, structure projects, set direction, prioritize tasks, or organize development workflows. Applies Linear's principles of momentum, simplicity, and focus—not API integration. For solo developers and teams organizing software projects.

Build an ROI calculator or value model for deals. Inputs: cost savings, efficiency gains, revenue impact. Output: ROI %, payback period, value summary. Trigger with "create ROI calculator for [deal/segment]", "value model for [product]", or use the /create-roi-calculator command.

Get or structure a sales playbook from ~~knowledge base~~ or context. Repeatable motions (who, when, how, assets) for discovery, demo, negotiation, and closing. Trigger with "get sales playbook", "what's our playbook for [motion]", or use the /get-sales-playbook command.

Research markets and segments: TAM/SAM/SOM, trends, drivers, and competitive landscape. Use when sizing a market or preparing founder-level market context.

Use this skill when the user asks to save, remember, recall, or organize memories. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories', 'stop here', 'pause this', 'record this', 'log this'. Also use proactively when discovering valuable findings worth preserving.

Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.

Decomposes a plan file into beads with epics, dependencies, and self-documenting context. Use when you have a comprehensive feature specification or implementation plan that needs to be broken into actionable, trackable tasks for multi-agent execution.

Systematic gap analysis for claimed vs actual work completion. Uses 100+ sequential thoughts to identify assumptions, partial completions, missing components, and rationalization patterns. Validates completion claims against original plans, detects scope deviations, reveals quality gaps. Essential for self-assessment before declaring work complete. Use when: claiming completion, final reviews, quality audits, detecting rationalization patterns in own work.

This skill should be used when starting a marimo development server with hot reload. Triggers include: - Starting marimo server - Running marimo notebooks locally - Launching marimo development environment - Setting up hot reload for notebooks

Create self-sufficient skills following Agent Skills standard. Use when building autonomous capabilities with progressive disclosure. Do not use for general programming or non-Claude contexts.

Health dimensions, score factors, and risk flags for customer accounts. Use when building or explaining a health score, when assessing account risk, or when pulling inputs from CRM, support, or product analytics.

Master GraphQL core concepts - types, queries, mutations, and subscriptions

Zod 4 schema validation patterns. Trigger: When creating or updating Zod v4 schemas for validation/parsing (forms, request payloads, adapters), including v3 -> v4 migration patterns.