Stats
Actions
Tags
From meta-skills
Mandatory protocol for checking and using applicable skills on every task. Use as your first action before responding to any user request - check the complete skill library (26 available skills organized by category), identify which skills apply, execute them with the Skill tool, announce usage, and follow all instructions precisely. Default behavior unless user explicitly says "skip skills", "don't use skills", "just answer", or similar override.
How this skill is triggered — by the user, by Claude, or both
Slash command
/meta-skills:using-superpowersThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill establishes a mandatory workflow for every task: **check for applicable skills first, then use them systematically**. It turns your entire skill library into an active decision system rather than a passive resource.
This skill establishes a mandatory workflow for every task: check for applicable skills first, then use them systematically. It turns your entire skill library into an active decision system rather than a passive resource.
Default behavior: For every task, check skills automatically UNLESS the user explicitly overrides.
Before responding to ANY request, ask yourself:
Examples of skill triggers:
landing-page-guide + landing-page-copywritermake-comfacebook-ads-skill or competitive-ads-extractorpptxemail-marketing-automation-skillIf a skill applies:
Tell the user which skill you're using and why.
Format: "I'm using the [Skill Name] to [what you're doing]."
Examples:
This transparency helps catch errors early and confirms you actually read the skill.
Execute the skill as documented:
Provide results that follow the skill's quality standards and output format.
For every task → check skills → use applicable ones
User can explicitly disable skill checking by saying ANY of these:
When user explicitly overrides: Respond directly without checking skills.
This is not negotiable, not optional, not subject to rationalization.
Apply this decision rule:
Why: Skills document proven techniques that prevent known errors and save time. Skipping them means repeating solved problems.
You might remember a skill from earlier, but skills evolve. Always read the current SKILL.md.
This prevents: Outdated knowledge, missed improvements, broken workflows.
If a skill has a checklist:
Why: Checklists without tracking = steps get skipped. Every time. The overhead is minimal compared to missing steps.
When user says "Add X" or "Fix Y", that's the WHAT.
The HOW comes from skills: brainstorming before coding, TDD workflows, verification steps, etc.
Red flags for skipping process:
If you catch yourself thinking ANY of these, STOP. You're rationalizing. Check for and use the skill.
| Rationalization | Truth |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I can check files quickly" | Files lack context. Check for skills. |
| "Let me gather info first" | Skills tell you HOW to gather info. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read the current version. |
| "This isn't a task" | If you're taking action, it's a task. Check skills. |
| "This skill is overkill" | Skills prevent hidden complexity. Use it. |
| "I'll just do this one thing first" | Check skills BEFORE doing anything. |
| "I read that skill recently" | Skills change. Read it fresh every time. |
| Need | Skill Category | Trigger Words |
|---|---|---|
| Create/edit documents | Documents | Create word doc, edit PDF, make slides, build spreadsheet |
| Write marketing copy | Content/Copywriting | Landing page copy, sales pitch, value proposition |
| Design visuals | Design | Poster, UI design, website layout, theme |
| Build ads | Marketing | Facebook ads, campaign, targeting, ROAS |
| Email automation | Marketing | Email sequence, drip campaign, nurture |
| Build workflows | Automation | Make scenario, automate process, integration |
| Test websites | Testing | Screenshot, test link, fill form, validate |
| Complex decision | Problem-solving | High stakes, validate architecture, deep analysis |
| Build interactive code | Artifacts | React component, dashboard, data visualizer |
| Create new skill | Meta | Build skill, create custom workflow |
This protocol is ACTIVE by default for all new tasks and conversations.
State assumptions:
Key principles:
For every task:
Override: User says "skip skills" → respond directly.
Confidence: This protocol exists because it works. Use it.
npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin meta-skillsGuides you to the best skill for your task, recommends skill combinations, and helps discover capabilities you didn't know you had.
Turns repeatable prompts or AI workflows into structured SKILL.md files for the affiliate-skills GitHub repository. Use when someone wants to create, write, share, or publish a skill.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.