Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Investigates what went wrong in a superpowers session by reading its transcript, reports findings with path and line citations, and can draft a GitHub issue or redacted bundle.
SKILL.md written in Chinese; this summary is our English description.
Install Diagnosing Superpowers Sessions
$ npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jnMetaCode/superpowers-zh diagnosing-superpowers --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/diagnosing-superpowers .claude/skills/diagnosing-superpowers && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "diagnosing-superpowers" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowers into .claude/skills/diagnosing-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnosing-superpowers", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jnMetaCode/superpowers-zh diagnosing-superpowers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/diagnosing-superpowers .agents/skills/diagnosing-superpowers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diagnosing-superpowers" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowers into .agents/skills/diagnosing-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnosing-superpowers", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jnMetaCode/superpowers-zh diagnosing-superpowers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/diagnosing-superpowers .cursor/skills/diagnosing-superpowers && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "diagnosing-superpowers" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowers into .cursor/skills/diagnosing-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnosing-superpowers", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jnMetaCode/superpowers-zh.git --path skills/diagnosing-superpowers--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jnMetaCode/superpowers-zh diagnosing-superpowers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/diagnosing-superpowers .gemini/skills/diagnosing-superpowers && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "diagnosing-superpowers" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowers into .gemini/skills/diagnosing-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnosing-superpowers", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jnMetaCode/superpowers-zh diagnosing-superpowersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/diagnosing-superpowers .github/skills/diagnosing-superpowers && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "diagnosing-superpowers" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowers into .github/skills/diagnosing-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnosing-superpowers", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jnMetaCode/superpowers-zh diagnosing-superpowers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/diagnosing-superpowers .opencode/skills/diagnosing-superpowers && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "diagnosing-superpowers" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/diagnosing-superpowers into .opencode/skills/diagnosing-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnosing-superpowers", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
diagnosing-superpowers- GitHub stars
- 8.3k
- Token cost
- ~858 tokens
- SKILL.md length
- 177 words
- Files
- 20 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Investigates what went wrong in a superpowers session by reading its transcript, reports findings with path and line citations, and can draft a GitHub issue or redacted bundle.
- Works in 7 steps: 问题受理。 一次只问一个问题，直到你能写出一段陈述：点名是哪个（些）会话、 → 定位。 按 references/session-discovery.md… → 分诊。 先亲自读报告问题附近的那一段。然后为每个维度并行派发一个分析员子智能体， → …
- Finding out why a superpowers session repeated work or ignored the plan
- SKILL.md covers 概述, 工作流, 速查 and 硬性规则, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill, written in Chinese, helps you work out why a superpowers session went badly, for example repeated work, a plan being ignored, a skill that never triggered, slow progress or high cost. It reads the session transcript from disk and reports evidence instead of diagnosing superpowers itself. Every finding must cite path:line, and every number must come from the transcript or from a command the agent ran.
The workflow starts with intake questions, then locates each session and fills in a case file. Seven analyst subagents run in parallel, one each for skill timeline, plan adherence, repeated work, stumbles, quality evidence, request conflicts and cost and time. A report follows. On request it also searches existing GitHub issues, drafts an issue that is created only after approval, builds a redacted bundle at skeleton, evidence or full level, and looks for similar sessions. Session files are only ever read, never changed.
When your agent uses it
- Finding out why a superpowers session repeated work or ignored the plan
- Explaining why a session was slow or expensive using transcript evidence
- Checking whether a particular skill never triggered during a session
- Preparing a redacted bug report bundle for superpowers maintainers
Example prompts
- “Why did yesterday's session redo the same refactor twice? Diagnose it from the transcript.”
- “This session feels slow and expensive, so find out where the time and tokens went.”
- “Put together a bug report for the superpowers maintainers from this session, with a redacted bundle.”
Requirements
- Access to the session transcript files on disk
- The `gh` CLI, for the optional GitHub issue steps
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- 问题受理。 一次只问一个问题，直到你能写出一段陈述：点名是哪个（些）会话、
- 定位。 按 references/session-discovery.md 把每个会话解析成经过核实的
- 分诊。 先亲自读报告问题附近的那一段。然后为每个维度并行派发一个分析员子智能体，
- 报告。 按顺序填写 templates/report.md 的每一节，写入工作区，展示出来，
- GitHub issue —— 当报告 §7 写的是 possible 或 likely，或你的伙伴要求时。
- 导出 —— 只在你的伙伴要求打包时进行；绝不主动打包。如果受理时的目标是 bug
- 相似会话 —— 被要求时进行。把已确认的发现转成一个特征签名，按修改时间和大小
What it can do on your machine
Read from SKILL.md and the folder at commit 2daf57c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Diagnosing Superpowers Sessions loads about 858 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 177 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jnMetaCode/superpowers-zh at commit 2daf57c, republished under its MIT licence (© jnMetaCode). 177 words, ~858 tokens.
Download SKILL.mdSave it as
.claude/skills/diagnosing-superpowers/SKILL.md (or your agent's skills folder). This skill also uses 19 other files; get the full folder from GitHub.- name
- diagnosing-superpowers
- description
- 当一次 superpowers 会话出了问题、你的人类伙伴想知道原因时使用——重复劳动、无视计划、磕磕绊绊、结果质量差、某个技能没触发、"太慢了"、"为什么这么贵"、"它到底在干什么"——或者想给 superpowers 维护者整理一份 bug 报告；适用于当前会话，或按 id / 路径指定的过往会话，任何工具均可
- version
- 1.0.0
- license
- MIT
诊断 Superpowers
概述
和你的人类伙伴一起明确一次会话到底哪里出了问题，读取磁盘上的会话记录（transcript）， 用证据报告发生了什么。你负责报告，不负责诊断 superpowers。superpowers 要不要改， 由分诊这份打包材料或这条 issue 的人决定。
核心原则： 每条发现都要引用 path:line。没有引用，就不算发现。每个数字都来自
会话记录或你亲自跑过的命令，绝不凭记忆。
工作流
每一步建一个待办。第 5–7 步只在各自注明的条件下执行。
- 问题受理。 一次只问一个问题，直到你能写出一段陈述：点名是哪个（些）会话、 已知的话给出轮次范围、你的伙伴期望什么、实际发生了什么、他们关心的可观测量 （耗时、token、重复动作、某一个具体动作）。"太慢了"是抱怨，不是问题陈述。 记下目标是否是一份 superpowers bug 报告。
- 定位。 按
references/session-discovery.md把每个会话解析成经过核实的 绝对文件系统路径。确认过往会话时，引用它的第一条提示词和时间戳，并列出你排除的 每个候选及理由，没有就写"none"。枚举子智能体的会话记录。创建~/.superpowers/diagnosing-superpowers/<session-id>/，把路径告诉你的伙伴， 在其中填写templates/case.md，环境与技能观察遵循其中的来源标注规则。 - 分诊。 先亲自读报告问题附近的那一段。然后为每个维度并行派发一个分析员子智能体，
每个都给它：案例文件路径、
prompts/analyst-common.md，以及prompts/下的一个 维度文件：skill-timeline.md、plan-adherence.md、repeated-work.md、stumbles.md、quality-evidence.md、request-conflicts.md、cost-and-time.md。 会话记录很长时，按轮次范围拆分一个维度。凡是返回的发现没有path:line，一律丢弃。 - 报告。 按顺序填写
templates/report.md的每一节，写入工作区，展示出来， 并给出路径。核对被引用的内容实际能证明什么，并保留支撑它的案例；符号链接别名 不算冗余副本。 - GitHub issue —— 当报告 §7 写的是 possible 或 likely，或你的伙伴要求时。
按
references/github-issues.md在已开放和已关闭的 issue 中搜索这些症状。 展示匹配结果，建议把报告补充到最接近的那条。如果都不匹配，填写templates/issue.md，写入工作区，展示确切文本，获得批准后才创建 issue。gh不能附加文件；如果有打包材料，把路径给你的伙伴，让他们在浏览器里附上。 - 导出 —— 只在你的伙伴要求打包时进行；绝不主动打包。如果受理时的目标是 bug
报告，说一次"可以按需提供脱敏后的打包材料"，然后等待。询问脱敏级别，并说明每一级
包含什么：skeleton（不含工具结果正文）、evidence（只含被引用事件的正文）、full。
按
templates/bundle-README.md构建打包材料，派发prompts/scrub.md，再派发prompts/scrub-audit.md，两者反复执行，直到审计返回 CLEAN。 先完成打包模板里的证据核对与对账，再展示最终的脱敏日志、文件清单，以及隐私与 证据两方面的结论。获得批准后才归档（zip -r或tar -czf）。给出归档路径时， 说明其中包含什么，指向脱敏日志查看替换情况，并说明脱敏可能有遗漏：他们必须在 分享前逐个审阅每个文件。 - 相似会话 —— 被要求时进行。把已确认的发现转成一个特征签名，按修改时间和大小
列出候选，找到标记所在的行号，对每个候选并行派发
prompts/similar-session.md， 然后追加到报告 §9。
速查
七个分析员始终全部运行。这张表说明第 3 步里你自己先读哪一段，以及结论中先讲哪些发现。
| 抱怨 | 先读、先讲 |
|---|---|
| "太慢了" | cost-and-time、stumbles |
| "它为什么做了额外的活？" | repeated-work、plan-adherence |
| "为什么这么贵？" | cost-and-time |
| "它到底在干什么？"（仍在运行） | skill-timeline；在覆盖说明中注明仍在进行 |
| "它无视了计划" | plan-adherence，先看压缩（compaction）所在行 |
| "技能 X 从没触发" | skill-timeline |
硬性规则
- 上下文安全。 一行会话记录就可能有一兆字节。每个会话文件、每一次，都要遵循
references/context-safety.md。 - 只读。 绝不修改、移动或删除会话文件。
- 给子智能体确切路径。 子智能体的"当前会话"是它自己的会话。传绝对路径和 id。
- 只认人类提示词。 hook 输出、system reminder 和工具结果都不是你伙伴说的话。 在子智能体的会话记录里，"user" 是父智能体。
- 不诊断 superpowers。 报告 §7 只陈述是否涉及，到此为止。绝不指出某个技能的缺陷， 也不提议修改。你的伙伴催着要修复，也不能豁免这一条；指向 issue 那一步，并提一句 可以按需提供打包材料。也不要给你的伙伴提建议。
- 批准关卡。 你的伙伴看过脱敏日志和文件清单之前，不归档。他们批准确切文本之前， 不发 issue 或评论。
- 先受理，后分析。 你的伙伴答复之前，第 2–7 步一律不开始。如果他们不在，写下问题 然后停下。你替他们重构出来的陈述不算答复。一个范围已经明确的请求——某个具体事件、 现在正在运行什么、或者要跑哪项分析——本身就是陈述：先回答它，再提问。 针对整个会话的"为什么"是抱怨。
危险信号
| 想法 | 现实 |
|---|---|
| "问题很明显，跳过受理" | 问题陈述决定了一切的范围。去问。 |
| "他们不在，那我来重构陈述" | 你无法重构他们想要什么。写下问题，然后停下。 |
| "我先全部扫一遍，最后再问" | 无范围的扫描会把他们的预算花在错误的问题上。先问。 |
| "他们要 bug 报告，那我现在就打包" | 打包材料就是他们打包起来的会话数据。只在他们要求时才构建。 |
| "只是个小的定点修改，不用重构" | 再小也不归你决定。报告证据；由分诊的人决定。 |
| "每个 token 的价格众所周知" | 不是从会话记录里算出来的数字就是编造的。要么引用，要么删掉。 |
© jnMetaCode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 19 other files (references) in skills/diagnosing-superpowers of jnMetaCode/superpowers-zh.
- SKILL.md
- prompts/analyst-common.md
- prompts/cost-and-time.md
- prompts/plan-adherence.md
- prompts/quality-evidence.md
- prompts/repeated-work.md
- prompts/request-conflicts.md
- prompts/scrub-audit.md
- prompts/scrub.md
- prompts/similar-session.md
- prompts/skill-timeline.md
- prompts/stumbles.md
- references/context-safety.md
- references/github-issues.md
- references/redaction-policy.md
- references/session-discovery.md
- templates/bundle-README.md
- templates/case.md
- … and 2 more
Open the folder on GitHubat commit 2daf57c
Compare with similar skills
Diagnosing Superpowers Sessions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Diagnosing Superpowers Sessions this skilljnMetaCode/superpowers-zh | 8.3k | — | ~858 | Automated safety check: Pass | MIT | |
| Diagnosing Superpowers Sessionsobra/superpowers | 297k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Copilot Session Failure Analysisdotnet/maui | 23k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Kayba Pipelinekayba-ai/agentic-context-engine | 2.6k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Operational Value Designergithub/gh-aw | 5.4k | — | ~6.8k | Automated safety check: Pass | MIT | |
| Badstephenleo/bmad-autonomous-development | 107 | — | ~7.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Copilot Session Failure Analysis
dotnet/maui
Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.
Kayba Pipeline
kayba-ai/agentic-context-engine
End-to-end agent evaluation and improvement pipeline. An agent skill from kayba-ai/agentic-context-engine.
- Official
Operational Value Designer
github/gh-aw
Designs and verifies a deterministic grader that measures whether a GitHub Agentic Workflow run reached its real-world or repository outcome.
Bad
stephenleo/bmad-autonomous-development
BMad Autonomous Development — orchestrates parallel story implementation pipelines.
Analyze Trajectory
yologdev/yoyo-evolve
Diagnoses a recurring failure such as a stuck task, repeated CI error or frequent reverts by sending sub-agents through the logs and returning one root-cause diagnosis.
More from jnMetaCode/superpowers-zh
All 21 skills in this repoBrainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
Git Worktree Isolation
jnMetaCode/superpowers-zh
Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.
Inline Plan Execution
jnMetaCode/superpowers-zh
Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.
Chinese Code Review Etiquette
jnMetaCode/superpowers-zh
Gives Chinese-language templates and priority labels for code review feedback, plus guidance on bilingual comments, commit messages and common team anti-patterns.
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
Chinese Documentation Style Guide
jnMetaCode/superpowers-zh
Reference rules for typesetting Chinese technical documents: spacing around English and digits, punctuation, term handling, bilingual API docs and README layout.
Related
Works with
Categories
Questions about Diagnosing Superpowers Sessions
What does Diagnosing Superpowers Sessions do?
Investigates what went wrong in a superpowers session by reading its transcript, reports findings with path and line citations, and can draft a GitHub issue or redacted bundle. This skill, written in Chinese, helps you work out why a superpowers session went badly, for example repeated work, a plan being ignored, a skill that never triggered, slow progress or high cost. It reads the session transcript from disk and reports evidence instead of diagnosing superpowers itself.
When should I use Diagnosing Superpowers Sessions?
Diagnosing Superpowers Sessions fits situations like: finding out why a superpowers session repeated work or ignored the plan; explaining why a session was slow or expensive using transcript evidence; checking whether a particular skill never triggered during a session; preparing a redacted bug report bundle for superpowers maintainers.
How do I install Diagnosing Superpowers Sessions in Claude Code?
Run `npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a claude-code`. Or copy the skill folder (skills/diagnosing-superpowers in jnMetaCode/superpowers-zh) into .claude/skills/diagnosing-superpowers in your project. Claude Code loads it when a task matches its description.
How do I install Diagnosing Superpowers Sessions in Codex?
Run `npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a codex`. Or copy the skill folder (skills/diagnosing-superpowers in jnMetaCode/superpowers-zh) into .agents/skills/diagnosing-superpowers in your project. Codex loads it when a task matches its description.
Can I use Diagnosing Superpowers Sessions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jnMetaCode/superpowers-zh --skill diagnosing-superpowers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnosing-superpowers, .gemini/skills/diagnosing-superpowers, .github/skills/diagnosing-superpowers and .opencode/skills/diagnosing-superpowers in your project.
What does Diagnosing Superpowers Sessions need to run?
SKILL.md names no scripts, command-line tools or credentials: Diagnosing Superpowers Sessions is instructions for the agent only. Our summary lists: Access to the session transcript files on disk; The `gh` CLI, for the optional GitHub issue steps.
Does Diagnosing Superpowers Sessions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Diagnosing Superpowers Sessions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Diagnosing Superpowers Sessions use?
Diagnosing Superpowers Sessions is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Diagnosing Superpowers Sessions use?
About 858 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Diagnosing Superpowers Sessions?
Skills that share tags, products or a category with Diagnosing Superpowers Sessions: Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Copilot Session Failure Analysis (dotnet/maui, 23k stars), Kayba Pipeline (kayba-ai/agentic-context-engine, 2.6k stars) and Operational Value Designer (github/gh-aw, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Diagnosing Superpowers Sessions?
jnMetaCode (a GitHub user) maintains it in jnMetaCode/superpowers-zh, which has 8,280 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.
Source: jnMetaCode/superpowers-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.