using-superpowers

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill using-superpowers-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/using-superpowers
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill using-superpowers-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents often skip available skills and improvise answers, producing inconsistent results. This Skill establishes a mandatory workflow that forces the agent to check for and invoke relevant skills before responding, asking clarifying questions, or exploring a codebase. ## Core Features & Use Cases - Mandatory Skill-First Rule: Requires invoking any potentially relevant skill before any response, with a red-flags table that catches common rationalizations for skipping skills. - 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 that translate skill actions (subagent dispatch, task tracking, file operations) into the native tools of Codex, Gemini CLI, Pi, Antigravity, and Hermes Agent. - Use Case: When a user says "fix this bug", the agent invokes the systematic-debugging skill first instead of jumping straight into editing files. ## Quick Start Ask the agent to start any task and it will check for applicable skills and announce which one it is using 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 invoke any relevant skill before responding, asking 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 it out. For example, brainstorming runs before frontend-design, and systematic-debugging runs before domain-specific fix skills.

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

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

When should a skill be skipped during a task?

Only when the user explicitly instructs skipping it, or when the agent was dispatched as a subagent for a specific task. User instructions in files like CLAUDE.md or AGENTS.md take precedence over skill workflows.

Why does the agent invoke a skill even for simple questions?

The skill treats every question and action as a task that may have an applicable skill. Its red-flags table lists common rationalizations, like assuming a question is too simple, as signals to stop and check for skills first.