using-superpowers

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill using-superpowers-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/using-superpowers
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill using-superpowers-base-analitica

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 guidance. This Skill establishes a mandatory rule that relevant skills must be invoked before any response, including clarifying questions or codebase exploration. ## Core Features & Use Cases - Mandatory Skill Invocation: Requires checking for and invoking applicable skills before any response or action, with a red-flags table that counters common rationalizations for skipping. - Skill Priority Ordering: Defines that process skills (like brainstorming or systematic-debugging) run before implementation skills when multiple skills apply. - Cross-Platform Tool Mapping: Ships reference files mapping generic skill actions (dispatch subagent, create todo, read file) to concrete tools on Codex, Gemini CLI, Antigravity, Hermes Agent, and Pi. - Use Case: When a user says "fix this bug", the agent first invokes the systematic-debugging skill before touching any code, ensuring a disciplined debugging process. ## Quick Start Start a new conversation and let this skill check for applicable skills before answering any request.

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 the correct order when multiple skills apply to a task?▼

Process skills come first because they set the approach, then implementation skills carry out the work. For example, brainstorming runs before frontend-design when building something new, and systematic-debugging runs before domain skills when fixing a bug.

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

Yes. It includes reference files mapping generic skill actions to concrete tools on Codex, Gemini CLI, Antigravity, Hermes Agent, and Pi, covering subagent dispatch, task tracking, and file operations for each platform.

When should a skill be skipped during a task?▼

Only when a subagent was dispatched for a specific task, or when explicit user instructions in files like CLAUDE.md or AGENTS.md override the skill workflow. Otherwise, even a small chance of applicability requires invocation.

Why does the agent keep answering without invoking any skills?▼

Common causes are rationalizations like treating the request as a simple question or exploring files first. The skill's red-flags table explicitly counters these patterns and requires the skill check to happen before any other action.