using-superpowers

Enforces skill discovery and invocation before any agent response or action.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill using-superpowers-thienty1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/superpowers/using-superpowers
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill using-superpowers-thienty1207

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents often skip available skills and improvise answers, leading to inconsistent workflows and missed process steps. This Skill establishes a mandatory rule that relevant skills must be invoked before any response, clarifying question, or codebase exploration. ## Core Features & Use Cases - Mandatory Skill Invocation: Requires checking for and invoking applicable skills before any action, with a red-flags table that catches common rationalizations for skipping them. - Skill Priority Ordering: Defines that process skills (like brainstorming or systematic-debugging) run before implementation skills when multiple skills apply. - Platform Adaptation: Ships reference files mapping generic skill actions (subagent dispatch, task tracking) to concrete tools on Codex, Gemini CLI, Pi, and Antigravity. - Use Case: When a user says "fix this bug", the agent invokes the systematic-debugging skill first instead of immediately editing code, ensuring a disciplined root-cause process. ## Quick Start Start a new conversation and ask the agent to build or fix something, and it will invoke the relevant skill before responding.

Frequently Asked Questions about using-superpowers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent always use skills before responding?

Install this skill so it loads at conversation start. It instructs the agent to check for and invoke any relevant skill before responding, asking clarifying questions, or exploring files, and to announce which skill it is using.

What is skill priority when multiple skills apply to a task?

Process skills run first because they set the approach, then implementation skills carry out the work. For example, brainstorming precedes frontend-design for build requests, and systematic-debugging precedes domain skills for bug fixes.

Does this skill work with Codex, Gemini CLI, and other agent harnesses?

Yes. It includes reference files that map generic skill actions to platform tools: spawn_agent for Codex, invoke_agent for Gemini CLI, task artifacts for Antigravity, and optional subagent extensions for Pi.

When should a skill not be invoked before acting?

Subagents dispatched for a specific task ignore this skill, and explicit user instructions such as CLAUDE.md or AGENTS.md take precedence over skill workflows. Otherwise, even a small chance of relevance requires invocation.

Why does the agent keep asking to invoke a skill for simple questions?

The skill treats every question and action as a task requiring a skill check, since simple requests often become complex. The red-flags table explicitly lists rationalizations like "this is just a simple question" as signals to stop and check.