Loading...
Loading...
Found 66 Skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Forge implementation from JIRA tickets using dynamic skill generation. Gathers context into a lazy-loaded skill, then invokes it for execution. Use when given a JIRA ticket URL (format: https://[domain].atlassian.net/browse/[TICKET-ID]) to process end-to-end.
Implements the corrections found by /project-audit. Reads audit-report.md as spec and executes each required action. Trigger: /project-fix, apply audit corrections, fix claude project.
SEO & Content Marketing skill suite for Claude with keyword research, content audits, technical SEO, and structured workflows
Set up and manage local skills for automatic matching and invocation
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.
Show whether each skill is earning its context-window cost — combined tokens-used view sorted by waste. Use when the user asks 'are my skills worth it', 'what's my context budget', 'which skills are dead weight', or wants to audit skill value, token cost, or usage. Trigger with '/janitor-value'.
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
SEO & Content Marketing skill suite with keyword research, content audits, technical SEO, and SERP analysis commands for Claude Code
Use when creating new skills, editing existing skills, or verifying the validity of skills before deployment
Session orientation and awareness — retro summaries, handoffs, git state, focus. Use when starting a session, after /jump, lost your place, switching context, or when user asks "now", "where are we", "what are we doing", "status", "recap". Do NOT trigger for "standup" or "morning check" (use /standup), or session mining "dig", "past sessions" (use /dig).
Search existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.