Skip to content

Skill Trigger Keyword Map

Skills fire either via /slash invocation or via keyword auto-triggers defined in CLAUDE.md. Priority levels P0–P3 determine how aggressively Claude routes a request.

P3 · Niche

keybindings → /keybindings-help

P2 · On-Request

docx → /docx

pdf → /pdf

xlsx → /xlsx

history → /session-logs

P1 · High Priority

Anthropic SDK →

/claude-api

UI work →

/gstack

CH outreach →

/acquisitions-outreach

Buyer blast →

/dispo-blast

P0 · Auto-Invoke

Plan keywords →

/gsd:plan-phase

Execution keywords →

/gsd:execute-phase

Plan written →

/plan-eng-review

Endpoint changes →

/security-review

User Input Forms

/slash command

Keyword in chat

File event

(opens .ipynb, edits PR)

Trigger condition met

(plan written, phase done)

CLAUDE.md

Tool Trigger

Conditions table

TierWhen it firesExample
P0Auto-invoke on critical execution, governance, or safety paths/security-review fires automatically when a webhook handler is modified
P1High-leverage workflows — keyword match in chat OR explicit slash/acquisitions-outreach fires on “send initial CH outreach”
P2Domain-specific helpers, on-request/docx fires when you mention “Word doc”
P3Niche customization/keybindings-help fires for “rebind shortcut”

The full Tool Trigger Conditions table is in CLAUDE.md under “Tool Trigger Conditions (auto-invoke, no memory required)”. ~80 entries spanning P0-P3.

~/.claude/skills/ has ~94 directories. ~54 with valid SKILL.md frontmatter. Each skill is a self-contained YAML+markdown bundle Claude can load and execute.

For a deeper explainer of how skills work, see Skills Primer.