using-superpowers

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

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill using-superpowers-viranya2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/using-superpowers
Command: npx skills add https://github.com/Viranya2006/Lumen --skill using-superpowers-viranya2006

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 located and invoked before any response, clarifying question, or codebase exploration. ## Core Features & Use Cases - Mandatory Skill-First Rule: Requires checking for and invoking applicable skills before any action, with a red-flags table that counters common rationalizations for skipping them. - Skill Priority Ordering: Defines that process skills (brainstorming, systematic-debugging) run before implementation skills when multiple skills apply. - Cross-Platform Tool Mapping: Ships reference files mapping skill actions (subagent dispatch, task tracking) to concrete tools on Codex, Gemini CLI, Pi, and Antigravity harnesses. - 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 workflow. ## Quick Start Start any conversation by checking which skills apply to the request and invoke the matching 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 use skills before responding?

Invoke this skill at conversation start so the agent checks for applicable skills before any response, including clarifying questions or codebase exploration. The rule treats every action as a task requiring a skill check first.

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 precedes frontend-design when building a feature, and systematic-debugging precedes domain skills when fixing a bug.

Does this skill work with Gemini CLI and Codex?

Yes, it includes reference files mapping skill actions to harness-specific tools. Gemini CLI uses activate_skill and invoke_agent, while Codex requires enabling multi_agent in config.toml for subagent dispatch.

When can a skill workflow be skipped?

Only when the user explicitly instructs skipping it. User instructions in files like CLAUDE.md, AGENTS.md, or GEMINI.md take precedence over skills, which in turn override default agent behavior.

Why does the agent ignore available skills during simple tasks?

Agents rationalize skipping skills with thoughts like "this is just a simple question" or "I need context first". The skill's red-flags table counters these by requiring a skill check before any action, since simple tasks often become complex.