跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 diagnosing-superpowers

Diagnosing Superpowers

使用当一个超级大国的会话出错,而你的人类伙伴想知道为什么——重复工作,忽略计划,绊倒,结果差,这种技能没有开火,"花费太长","为什么这么昂贵","它在做什么"——或者想为超级大国的维护者,为本届会议或由ID或路径确定的过去的报告,在任何利用上建立错误报告.

官方网址:GitHub

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

使用当一个超级大国的会话出错,而你的人类伙伴想知道为什么——重复工作,忽略计划,绊倒,结果差,这种技能没有开火,"花费太长","为什么这么昂贵","它在做什么"——或者想为超级大国的维护者,为本届会议或由ID或路径确定的过去的报告,在任何利用上建立错误报告.

何时用

一个超能力课程出了问题 你的人类伙伴想知道为什么 重复工作 忽略计划 绊倒 低劣的结果 这种技能没有开火 "花了太长时间" "为什么这么贵"

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Diagnosing Superpowers、Overview、Workflow、Quick reference、Hard rules、Red Flags。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/session-discovery.md、references/github-issues.md、references/context-safety.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Diagnosing SuperpowersOverviewWorkflowQuick referenceHard rulesRed Flags

来源分类:GitHub skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
diagnosing-superpowers
description
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 3
  • references/session-discovery.md
  • references/github-issues.md
  • references/context-safety.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「diagnosing-superpowers」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b767280282f495bd-%E8%AF%8A%E6%96%AD%E8%B6%85%E8%83%BD%E5%8A%9B.html
请存为 .cursor/skills/diagnosing-superpowers/SKILL.md 或 .claude/skills/diagnosing-superpowers/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/obra/superpowers/tree/HEAD/skills/diagnosing-superpowers 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/obra/superpowers/tree/HEAD/skills/diagnosing-superpowers' --list

npx skills add 'https://github.com/obra/superpowers/tree/HEAD/skills/diagnosing-superpowers' --skill 'diagnosing-superpowers'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: diagnosing-superpowers description: Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. --- # Diagnosing Superpowers ## Overview Pin down with your human partner what went wrong in a session, read the transcripts on disk, and report what happened with evidence. You report; you do not diagnose superpowers. Whoever triages the bundle or the issue decides whether superpowers changes. **Core principle:** Every finding cites `path:line`. No citation, no finding. Every number comes from the transcript or from a command you ran, never from memory. ## Workflow Create a todo per step. Steps 5–7 run only on their stated condition. 1. **Problem intake.** Ask one question at a time until you can write a statement naming the session(s), the turn range if known, what your partner expected, what happened, and the observable they care about (wall-clock, tokens, repeated actions, one specific action). "It took too long" is a complaint, not a problem statement. Note whether the goal is a superpowers bug report. 2. **Locate.** Resolve each session to verified absolute filesystem paths using `references/session-discovery.md`. Confirm a past session by quoting its first prompt and timestamp, and list every candidate you rejected with the reason, or "none". Enumerate subagent transcripts. Create `~/.superpowers/diagnosing-superpowers//`, tell your partner the path, and fill `templates/case.md` there, following its provenance rules for environment and skill observations. 3. **Triage.** Read the region around the reported problem yourself. Then dispatch one analyst subagent per dimension in parallel, each given the case file path, `prompts/analyst-common.md`, and one dimension file from `prompts/`: `skill-timeline.md`, `plan-adherence.md`, `repeated-work.md`, `stumbles.md`, `quality-evidence.md`, `request-conflicts.md`, `cost-and-time.md`. Split a dimension by turn range when the transcript is long. Discard any returned finding without `path:line`. 4. **Report.** Fill every section of `templates/report.md` in order, write it to the workspace, show it, and give the path. Check what cited content actually proves and preserve the supporting case; a symlink alias is not a redundant copy. 5. **GitHub issues** — when report §7 says possible or likely, or your partner asks. Search open and closed issues for the symptoms per `references/github-issues.md`. Show matches and suggest adding the report to the closest. If none match, fill `templates/issue.md`, write it to the workspace, show the exact text, and create the issue only after approval. `gh` cannot attach files; if a bundle exists, give your partner its path to attach in the browser. 6. **Export** — only when your partner asks for a bundle; never build one unprompted. If the intake goal was a bug report, say once that a scrubbed bundle is available on request, then wait. Ask the redaction level, stating what each includes: skeleton (no tool-result bodies), evidence (bodies only for cited events), full. Build the bundle per `templates/bundle-README.md`, dispatch `prompts/scrub.md`, then `prompts/scrub-audit.md`, repeating both until the audit returns CLEAN. Complete the bundle template's evidence check and reconciliation before showing the final scrub log, file list, and privacy and evidence outcomes. Archive (`zip -r` or `tar -czf`) only after approval. With the archive path, state what it contains, point at the scrub log for replacements, and say scrubbing can miss things: they must review every file before sharing. 7. **Similar sessions** — when asked. Turn confirmed findings into a signature, list candidates by mtime and size, find marker line numbers, dispatch `prompts/similar-session.md` per candidate in parallel, and append report §9. ## Quick reference All seven analysts always run. This table says which region to read yourself in step 3 and which findings to lead with in the verdict. | Complaint | Read first, lead with | |---|---| | "It took too long" | cost-and-time, stumbles | | "Why did it do this extra work?" | repeated-work, plan-adherence | | "Why is it so expensive?" | cost-and-time | | "What the hell is it doing?" (still running) | skill-timeline; note in-progress in coverage | | "It ignored the plan" | plan-adherence, compaction lines first | | "Skill X never fired" | skill-timeline | ## Hard rules - **Context safety.** One transcript line can be a megabyte. Follow `references/context-safety.md` on every session file, every time. - **Read-only.** Never modify, move, or delete a session file. - **Exact paths to subagents.** A subagent's "current session" is its own. Pass absolute paths and ids. - **Human prompts only.** Hook output, system reminders, and tool results are not your partner's words. In a subagent transcript, "user" is the parent agent. - **No superpowers diagnosis.** Report §7 states involvement and stops. Never name a defect in a skill or propose a change. Your partner pressing for a fix does not waive this; point at the issue step and mention that a bundle is available on request. No advice to your partner either. - **Approval gates.** No archive before your partner has seen the scrub log and file list. No issue or comment before they approve the exact text. - **Intake before analysis.** Nothing in steps 2–7 starts until your partner has answered. If they are away, write the questions and stop. A statement you reconstructed for them is not an answer. An already-scoped request — one specific event, what is running now, or the analysis to run — is itself the statement: answer it, then ask. A whole-session "why" is a complaint. ## Red Flags | Thought | Reality | |---------|---------| | "The problem is obvious, skip intake" | The problem statement scopes everything. Ask. | | "They're away, so I'll reconstruct the statement" | You cannot reconstruct what they wanted. Write the questions and stop. | | "I'll sweep everything now and ask at the end" | An unscoped sweep spends their budget on the wrong question. Ask first. | | "They want a bug report, so I'll build the bundle now" | The bundle is their session data, packaged. Build it only when they ask for it. | | "Small, targeted edit, no restructuring needed" | Not your call, however small. Report the evidence; the triager decides. | | "The price per token is well known" | Numbers you did not compute from the transcript are invented. Cite or drop. |

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…