Menu
Describes how to use abilities. Read before any conversation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Read this skill whenever you need to build a cli where the primary consumer is the agent.
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
Use when asked to create a new skillset.
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
| name | using-skills |
| description | Describes how to use abilities. Read before any conversation. |
After you've read a ability with Read tool, announce you're using it:
"I've read the [Skill Name] ability and I'm using it to [what you're doing]."
Examples:
Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the ability.
Many abilities contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some abilities are flexible patterns (architecture, naming). Adapt core principles to your context.
The ability itself tells you which type it is.
