Skip to content
Skills Library
AI & agents · Automation

using-superpowers

/using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill:// URL reading via the read tool before ANY response including clarifying questions

Repository
oh-my-pi ↗
Licence
MIT
Last repository change
09.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when starting any conversation - establishes how to find and use skills, requiring skill:// URL reading via the read tool before ANY response including clarifying questions

Original author description

Use when starting any conversation - establishes how to find and use skills, requiring skill:// URL reading via the read tool before ANY response including clarifying questions

How it works

  1. Instruction Priority
  2. How to Access Skills
  3. The Rule
  4. Red Flags
  5. Skill Priority
  6. Skill Types
  7. User Instructions
Original SKILL.md headings · 102 lines, 647 words
SKILL.md preview
---
name: using-superpowers
description: Use when starting any conversation - establishes how to find and use skills, requiring skill:// URL reading via the read tool before ANY response including clarifying questions
---

If you were dispatched as a subagent to execute a specific task, skip this skill.

<critical>
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST read 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.
</critical>

## Instruction Priority

These skills override default system prompt behavior, but **user instructions always take precedence**:

1. **User's explicit instructions** (AGENTS.md, direct requests) — highest priority
2. **These skills** — override default system behavior where they conflict
3. **Default system prompt** — lowest priority

If AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.

## How to Access Skills

Skills are listed in the system prompt by name and description. When a skill applies to your current task, read it via `skill://<skill-name>` using the `read` tool, then follow its instructions.

# Using Skills

## The Rule

**Read relevant or requested skills via skill:// URL BEFORE any response or action.** Even a 1% chance a skill might apply means that you should read it to check.

```dot
digraph skill_flow {
    "User message received" [shape=doublecircle];
    "About to EnterPlanMode?" [shape=doublecircle];
    "Already brainstormed?" [shape=diamond];
    "Invoke brainstorming skill" [shape=box];
    "Might any skill apply?" [shape=diamond];
    "Read skill:// URL" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create todo_write todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];

    "About to EnterPlanMode?" -> "Already brainstormed?";
    "Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
    "Already brainstormed?" -> "Might any skill apply?" [label="yes"];
    "Invoke brainstorming skill" -> "Might any skill apply?";

    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Read skill:// URL" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Read skill:// URL" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create todo_write todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create todo_write todo per item" -> "Follow skill exactly";
}
```

## 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. Read 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. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution

"Let's build X" → brainstorming first, then implementation skills.
"Fix this bug" → debugging first, then domain-specific skills.

## Skill Types

**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.

**Flexible** (patterns): Adapt principles to context.

The skill itself tells you which.

## User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.

Versions

RepositoryScoreLicence
This page · happyshittake/oh-my-pi100MIT
coco-research/coco100MIT
osmontero/opencode-skills100MIT
seaworld008/commonly-used-high-value-skills100MIT
chinkan/RustFox100MIT
VoDaiLocz/kilo-kit-mcp100Apache-2.0
sickn33/agentic-awesome-skills100MIT
liyunxuanyu/dsh-zcode-port100MIT
LiHongwei-cn/lihongwei-cn100MIT

Database snapshot: 13.11.2026 · package version 153225525b15 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100using-werkstatt
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 100using-ultraship
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 100using-systematic
    Use when starting any conversation - establishes how to find and use skills, requiring skill tool invocation before ANY response including clarifying questions
  • 100using-methodology
    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
  • 100using-quirk
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 100using-science-superpowers
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.