This entry duplicates using-superpowers, which is the one we list in search.

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Skill by KalarisLabs

IndexedApache-2.0★ 13

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/kalarislabs-using-superpowers

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name: using-superpowers
Description: Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
License: Apache-2.0
Instructions: 30 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific task, ignore this skill.
</SUBAGENT-STOP>

<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. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>

## The Rule

**Invoke relevant or requested skills BEFORE any response or action** — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.

**Before entering plan mode:** if you haven't already brainstormed, invoke the brainstorming skill first.

Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.

## Skill Priority

When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.

- "Let's build X" -> superpowers:brainstorming first, then implementation skills.
- "Fix this bug" -> superpowers:systematic-debugging first, then domain

From KalarisLabs/Skill-Doctor, Apache-2.0.

Signals

Stars: 13
Forks: 1
Open issues: 30
Last commit (this folder): Sep 10, 2026 (1 month ago)
Last release: Sep 12, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: Apache-2.0
Repository: github.com/KalarisLabs/Skill-Doctor
Website: github.com/KalarisLabs/Skill-Doctor
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from KalarisLabs

Cite this page

using-superpowers skill. Agent Mart. https://agentmart.dev/skills/kalarislabs-using-superpowers (last updated 2026-10-24)