diagnosing-superpowers
Diagnose Superpowers Session Failures
Coding-agent sessions can waste time without showing where behavior diverged. This skill analyzes transcripts and produces cited reports for review or issue filing.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "diagnosing-superpowers" from https://skillstore.io/skills/obra-diagnosing-superpowers.md and its manifest at https://skillstore.io/api/skills/obra-diagnosing-superpowers/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「diagnosing-superpowers」を使用しています。 Why did session abc123 repeat the same file reads?
期待される結果:
A repeated-work report listing grouped reads, intervening changes, turn ranges, evidence lines, and confidence for each finding.
「diagnosing-superpowers」を使用しています。 Why was this session expensive and slow?
期待される結果:
A cost summary covering supported token totals, longest turns, idle gaps, large tool results, compactions, and associated sessions.
「diagnosing-superpowers」を使用しています。 Prepare a report for the Superpowers maintainers.
期待される結果:
A cited diagnosis, related-issue results, an approved issue draft, and an optional scrubbed bundle with privacy limitations.
セキュリティ監査
安全All 44 static alerts are false positives caused by Markdown, templates, defensive redaction guidance, or bounded GitHub documentation. No prompt injection, credential access, arbitrary command execution, or unauthorized network destination was found. The workflow protects sensitive transcripts through read-only source handling, approval gates, redaction, and user review before sharing.
リスク要因
🌐 ネットワークアクセス (2)
📁 ファイルシステムへのアクセス (8)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/obra-diagnosing-superpowers/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/obra-diagnosing-superpowers?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/obra-diagnosing-superpowers?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/obra-diagnosing-superpowers/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/obra-diagnosing-superpowers.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
obra. (2026). diagnosing-superpowers security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/obra-diagnosing-superpowers/audits/1BibTeX形式の引用
@techreport{obra-obra-diagnosing-superpowers-2026,
author = {obra},
title = {diagnosing-superpowers security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/obra-diagnosing-superpowers/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "diagnosing-superpowers security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "obra"
date-released: "2026-09-24"
url: "https://skillstore.io/skills/obra-diagnosing-superpowers/audits/1"
identifiers:
- type: other
value: "skillstore:obra-diagnosing-superpowers:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Explain Unexpected Agent Work
Trace repeated commands, plan drift, errors, and unsupported completion claims in one coding session.
Analyze Cost and Delay
Measure supported token use, long turns, idle gaps, large tool results, and subagent activity.
Prepare a Maintainer Report
Create a cited report, search related issues, and prepare a scrubbed bundle after approval.
これらのプロンプトを試す
Diagnose this session: [session ID or path]. I expected [result], but observed [problem]. Focus on [observable].
Review [session] for repeated reads, edits, commands, searches, or decisions. Explain what changed between repetitions and cite every finding.
Analyze [session] for supported token use, longest turns, idle gaps, large tool results, compactions, and associated-session costs.
Prepare a Superpowers bug report for [session]. Search related issues, draft exact text, and offer a redacted evidence bundle for approval.
ベストプラクティス
- Provide the session identifier, expected result, observed problem, and observable that matters.
- Review every citation and redacted file before sharing a bundle.
- Approve exact issue text and archive contents only after checking the scrub log.
回避
- Do not request an unscoped sweep when one event or turn range matters.
- Do not treat current files or versions as proof of historical session state.
- Do not publish transcript bundles without independent review and explicit approval.