360 Secure SkillHub
360 安全技能中心

using-superpowers

一个技能调用治理 Skill:要求在任何回复、澄清或探索前先查找并调用相关技能,声明所用技能并遵循其清单;同时为 Codex、Pi、Antigravity 等环境提供适配参考文件。

eohmig
eohmig
热度 33.41
最近更新 2026-09-20 04:34:06
分类:自动化依赖:读写文件应用场景:工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add eohmig/using-superpowers
Metadata
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

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.

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 (if installed — not currently available in this collection).

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" → brainstorming first, then implementation skills.
  • "Fix this bug" → systematic-debugging first, then domain skills.

Red Flags

These thoughts mean STOP—you're rationalizing:

Thought Reality
"This is just a simple question" Questions are tasks. Check for skills.
"I need more context first" Skill check comes BEFORE clarifying questions.
"Let me explore the codebase first" Skills tell you HOW to explore. Check first.
"I can check git/files quickly" Files lack conversation context. Check for skills.
"Let me gather information first" Skills tell you HOW to gather information.
"This doesn't need a formal skill" If a skill exists, use it.
"I remember this skill" Skills evolve. Read current version.
"This doesn't count as a task" Action = task. Check for skills.
"The skill is overkill" Simple things become complex. Use it.
"I'll just do this one thing first" Check BEFORE doing anything.
"This feels productive" Undisciplined action wastes time. Skills prevent this.
"I know what that means" Knowing the concept ≠ using the skill. Invoke it.

Platform Adaptation

If your harness appears here, read its reference file for special instructions:

  • Codex: references/codex-tools.md
  • Pi: references/pi-tools.md
  • Antigravity: references/antigravity-tools.md

User Instructions

User instructions (AGENTS.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.