using-superpowers

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Using Superpowers

使用Superpowers

The Core Rule

核心规则

If there is even a 1% chance a skill applies to the current task, invoke it.

Skills are cheap to load. Failing to use an applicable skill is expensive.

如果有哪怕1%的可能性某个skill适用于当前任务，就调用它。

加载skill的成本很低，而未能使用适用的skill代价高昂。

How to Find Skills

如何查找Skill

At the start of every new task:

Review available skills (check

~/.openclaw/extensions/superpowers/skills/

)

Ask: "Does any skill match what I'm about to do?"
If yes → load and follow the skill exactly
If no → proceed with default behavior

In OpenClaw's persistent agent context, check skills at the start of every new task, not just new conversations. A long-running session may handle many different task types.

在每个新任务开始时：

查看可用的skill（检查

~/.openclaw/extensions/superpowers/skills/

路径）

自问：“是否有任何skill匹配我即将要做的事？”
如果是 → 加载并严格遵循该skill的指示
如果否 → 按默认行为继续

在OpenClaw的持久化Agent环境中，要在每个新任务开始时检查skill，而不仅仅是新对话开始时。一个长期运行的会话可能会处理多种不同类型的任务。

Decision Flowchart

决策流程图

New task received
    ↓
Does any skill apply? (even 1% chance → YES)
    ↓
YES → Announce: "Using [skill-name] to [purpose]"
      Load skill file
      Follow instructions exactly
      ↓
      Complete or hand off cleanly

NO → Proceed with default agent behavior

New task received
    ↓
Does any skill apply? (even 1% chance → YES)
    ↓
YES → Announce: "Using [skill-name] to [purpose]"
      Load skill file
      Follow instructions exactly
      ↓
      Complete or hand off cleanly

NO → Proceed with default agent behavior

Priority Hierarchy

优先级层级

User instructions — always highest priority
Skills — override default behavior when applicable
Default behavior — fallback when no skill applies

用户指令 — 始终是最高优先级
Skill — 适用时覆盖默认行为
默认行为 — 无适用skill时的 fallback

Announcing Skill Usage

宣布Skill的使用

When you invoke a skill, say so:

"Using
brainstorming
to explore approaches before writing code." "Using
systematic-debugging
to diagnose this error."

This keeps the human informed and lets them redirect if needed.

当你调用一个skill时，要告知：

"使用
brainstorming
技能在编写代码前探索解决方案。" "使用
systematic-debugging
技能诊断此错误。"

这能让用户了解情况，并在需要时进行引导。

OpenClaw-Specific Notes

OpenClaw特定说明

In persistent sessions, skills should be checked at the start of each new task, not just session start
Skills around
```
task-handoff
```
and
```
agent-self-recovery
```
matter more in OpenClaw than in session-based tools — don't skip them
If a task will take more than ~20 minutes, check
```
long-running-task-management
```
first

在持久化会话中，应在每个新任务开始时检查skill，而不仅仅是会话启动时
与
```
task-handoff
```
和
```
agent-self-recovery
```
相关的skill在OpenClaw中比在会话型工具中更重要——不要忽略它们
如果任务耗时将超过约20分钟，请先检查
```
long-running-task-management
```
skill