Agent skill · operations · davila7
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Why this skill is useful
Establishes a mandatory workflow for invoking skills, ensuring adherence to processes that enhance task execution.
What it needs
About 2k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT> How to Access Skills In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files. In other environments: Check your platform's documentation for how skills are loaded. Using Skills The Rule Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it. Red Flags These thoughts mean STOP—you're rationalizing: Thought Reality --------- --------- "This is just a simple question" Questions are tasks. Check for skills. "I need more context first" Skill check comes BEFORE clarifying questions. "Let me explore the codebase first" Skills tell you HOW to explore. Check first. "I can check git/files quickly" Files lack conversation context. Check for skills. "Let me gather information first" Skills tell you HOW to gather information. "This doesn't need a formal skill" If a skill exists, use it. "I remember this skill" Skills evolve. Read current version. "This doesn't count as a task" Action = task. Check for skills. "The skill is overkill" Simple things become complex. Use it. "I'll just do this one thing first" Check BEFORE doing anything. "This feels productive" Undisciplined action wastes time. Skills prevent this. "I know what that means" Knowing the concept ≠ using the skill. Invoke it. Skill Priority When multiple skills could apply, use this order: 1. Process skills first (brainstorming, debugging) - these determine HOW to approach the task 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/using-superpowers--527f12