Skills
Skills are reusable capabilities delivered as markdown files that teach Claude Code how to approach specific tasks. Every piece of Catalyst functionality — from committing code to researching a codebase — is a skill.
How Skills Work
Section titled “How Skills Work”There are two types of skills, distinguished by who activates them:
User-invocable skills are structured workflows you trigger with a slash command. They orchestrate multi-step processes — spawning agents, reading context, interacting with you, and saving artifacts.
Model-invocable skills are reference knowledge that Claude activates automatically when it detects relevant context. For example, when Claude sees a ticket ID like ACME-123, the linearis skill activates and teaches Claude how to use the Linearis CLI — without you having to explain it. These skills shape Claude’s behavior the way a README or style guide would, but they load on demand instead of consuming context all the time.
Some skills are both — they can be triggered by you or activated by Claude when relevant.
A third category, CI skills, are non-interactive variants designed for automation pipelines. They follow the same conventions but skip all user prompts.
For more on how Claude Code skills work under the hood, see Anthropic’s skills documentation.
Invoking Skills
Section titled “Invoking Skills”Type / followed by the skill name:
/research-codebase/commit/create-planClaude Code has excellent auto-complete — start typing /res and it will suggest /research-codebase. You don’t need to include the plugin name; Claude Code resolves skills across all installed plugins automatically.
Legend: User column: checkmark = invoke with /skill-name | Model column: checkmark = Claude activates automatically | CI = non-interactive, for automation pipelines
catalyst-dev
Section titled “catalyst-dev”The core development plugin. 23 skills covering research, planning, implementation, and shipping.
| Skill | User | Model | Description | Source |
|---|---|---|---|---|
research-codebase | ✓ | — | Parallel codebase research with specialized agents | Source |
create-plan | ✓ | — | Interactive implementation planning with phased structure | Source |
iterate-plan | ✓ | — | Revise existing plans with feedback or changed requirements | Source |
implement-plan | ✓ | — | Execute plans phase by phase with automated verification | Source |
validate-plan | ✓ | — | Verify implementation against plan success criteria | Source |
oneshot | ✓ | — | End-to-end: research, plan, implement in one invocation | Source |
commit | ✓ | — | Conventional commits with Linear ticket integration | Source |
create-pr | ✓ | — | Pull request creation with auto-generated description | Source |
describe-pr | ✓ | — | Generate or update PR descriptions from recent work | Source |
merge-pr | ✓ | — | Safe merge with verification and Linear status update | Source |
create-handoff | ✓ | — | Save session context for later resumption | Source |
resume-handoff | ✓ | — | Resume work from a handoff document | Source |
linear | ✓ | — | Direct ticket operations (create, update, comment) | Source |
create-worktree | ✓ | — | Create git worktree for parallel development | Source |
fix-typescript | ✓ | — | Fix TypeScript errors with strict anti-reward-hacking rules | Source |
scan-reward-hacking | ✓ | — | Scan for reward hacking patterns in recent changes | Source |
workflow-help | ✓ | — | Interactive guide to supported workflows | Source |
cycle-plan | ✓ | — | Plan work for current or next cycle | Source |
agent-browser | — | ✓ | Browser automation CLI reference — activates when browser testing is needed | Source |
code-first-draft | — | ✓ | Initial feature implementation guidance for rapid prototyping | Source |
linearis | — | ✓ | Linearis CLI reference — activates when working with ticket IDs like ACME-123 | Source |
ci-commit | — | CI | Non-interactive commits for automation pipelines | Source |
ci-describe-pr | — | CI | Non-interactive PR descriptions for automation pipelines | Source |
catalyst-pm
Section titled “catalyst-pm”Project management workflows. 40+ skills covering strategy, research, planning, and reporting.
Reporting & Analysis
Section titled “Reporting & Analysis”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
analyze-cycle | ✓ | — | Cycle health report with risk analysis and recommendations | Source |
analyze-milestone | ✓ | — | Milestone progress toward target dates | Source |
report-daily | ✓ | — | Quick daily standup summary | Source |
groom-backlog | ✓ | — | Backlog health analysis and cleanup | Source |
sync-prs | ✓ | — | GitHub-Linear PR correlation and gap identification | Source |
context-daily | ✓ | — | Context engineering adoption dashboard | Source |
Product Strategy
Section titled “Product Strategy”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
define-north-star | ✓ | — | Define north star metrics and strategic goals | Source |
write-prod-strategy | ✓ | — | Write product strategy documents | Source |
strategy-sprint | ✓ | — | Run a strategy sprint session | Source |
expansion-strategy | ✓ | — | Plan expansion and growth strategies | Source |
User Research
Section titled “User Research”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
interview-guide | ✓ | — | Create structured interview guides | Source |
interview-prep | ✓ | — | Prepare for user interviews | Source |
user-interview | ✓ | — | Conduct and document user interviews | Source |
interview-feedback | ✓ | — | Process and organize interview feedback | Source |
user-research-synthesis | ✓ | — | Synthesize findings from multiple research sessions | Source |
journey-map | ✓ | — | Create user journey maps | Source |
Feature Development
Section titled “Feature Development”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
prd-draft | ✓ | — | Create a modern PRD with guided questions and multi-agent review | Source |
prd-review-panel | ✓ | — | Multi-agent PRD review panel | Source |
feature-metrics | ✓ | — | Define and track feature-level metrics | Source |
feature-results | ✓ | — | Analyze feature launch results | Source |
launch-checklist | ✓ | — | Create comprehensive launch checklists | Source |
Experimentation
Section titled “Experimentation”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
experiment-decision | ✓ | — | Make data-driven experiment decisions | Source |
experiment-metrics | ✓ | — | Design experiment metrics and success criteria | Source |
impact-sizing | ✓ | — | Size the impact of proposed changes | Source |
Meetings & Communication
Section titled “Meetings & Communication”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
meeting-agenda | ✓ | — | Create structured meeting agendas | Source |
meeting-notes | ✓ | — | Transform meeting transcripts into structured action items | Source |
meeting-cleanup | ✓ | — | Clean up and organize meeting artifacts | Source |
meeting-feedback | ✓ | — | Process meeting feedback | Source |
slack-message | ✓ | — | Draft Slack messages for various contexts | Source |
status-update | ✓ | — | Generate status updates for stakeholders | Source |
Planning & Prioritization
Section titled “Planning & Prioritization”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
daily-plan | ✓ | — | Create daily work plans | Source |
weekly-plan | ✓ | — | Create weekly work plans | Source |
weekly-review | ✓ | — | Conduct weekly review sessions | Source |
prioritize | ✓ | — | Prioritize features and work items | Source |
Prototyping
Section titled “Prototyping”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
prototype | ✓ | — | Build quick prototypes | Source |
generate-ai-prototype | ✓ | — | Generate AI-powered prototypes | Source |
prototype-feedback | ✓ | — | Collect and organize prototype feedback | Source |
napkin-sketch | ✓ | — | Quick napkin-sketch ideation | Source |
Analysis
Section titled “Analysis”| Skill | User | Model | Description | Source |
|---|---|---|---|---|
competitor-analysis | ✓ | — | Conduct competitor analysis | Source |
retention-analysis | ✓ | — | Analyze user retention patterns | Source |
activation-analysis | ✓ | — | Analyze user activation funnels | Source |
metrics-framework | ✓ | — | Set up leading vs lagging indicators | Source |
| Skill | User | Model | Description | Source |
|---|---|---|---|---|
decision-doc | ✓ | — | Create structured decision documents | Source |
create-tickets | ✓ | — | Create Linear tickets from requirements | Source |
connect-mcps | ✓ | — | Connect and configure MCP servers | Source |
catalyst-analytics
Section titled “catalyst-analytics”PostHog integration for product analytics. ~40K token context cost — enable only when needed.
| Skill | User | Model | Description | Source |
|---|---|---|---|---|
analyze-user-behavior | ✓ | — | User behavior patterns and cohorts | Source |
segment-analysis | ✓ | — | User segment analysis for targeted insights | Source |
product-metrics | ✓ | — | Key product metrics and conversion rates | Source |
catalyst-debugging
Section titled “catalyst-debugging”Sentry integration for production error monitoring. ~20K token context cost — enable only when needed.
| Skill | User | Model | Description | Source |
|---|---|---|---|---|
debug-production-error | ✓ | — | Investigate production errors with Sentry data | Source |
error-impact-analysis | ✓ | — | Analyze error impact across users and releases | Source |
trace-analysis | ✓ | — | Trace error paths through the stack | Source |
catalyst-meta
Section titled “catalyst-meta”Workflow discovery and management for advanced users and plugin developers.
| Skill | User | Model | Description | Source |
|---|---|---|---|---|
discover-workflows | ✓ | — | Research external Claude Code repositories for workflow patterns | Source |
import-workflow | ✓ | — | Import and adapt workflows from other repositories | Source |
create-workflow | ✓ | — | Create new agents or skills from templates | Source |
validate-frontmatter | ✓ | — | Check frontmatter consistency across all workflows | Source |
audit-references | ✓ | — | Audit plugin health and find broken references | Source |
reorganize | ✓ | — | Analyze and reorganize directory structures | Source |