compose-doctor
Diagnose Goldsky Compose App Failures
Existing Compose apps can fail because of task errors, missing secrets, wallet settings, or deployment mismatches. This skill guides evidence-based diagnosis and proposes targeted fixes.
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "compose-doctor" from https://skillstore.io/skills/goldsky-io-compose-doctor.md and its manifest at https://skillstore.io/api/skills/goldsky-io-compose-doctor/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「compose-doctor」。 My local Compose app reports that a secret referenced in the manifest is missing.
預期結果:
Diagnosis: A required local secret is not configured. Fix: Add it through local secret management. Verify: Restart locally and check the logs.
正在使用「compose-doctor」。 My named wallet fails in local development because it has no private key.
預期結果:
Diagnosis: The named wallet cannot run in plain local mode. Options: Use fork mode or a suitable EOA wallet. Confirm before changing configuration.
正在使用「compose-doctor」。 My deployed task reports that a transaction receipt reverted.
預期結果:
Diagnosis: The onchain transaction reverted. Next step: Inspect the failed run trace for the decoded reason. Do not retry or fund automatically.
安全審計
中風險Most static matches are Markdown formatting, diagnostic examples, or scoped cache maintenance rather than malicious execution, credential theft, or reconnaissance. Confirmed risks include forced deployment, forced cleanup, and automatic pausing; a separate semantic finding covers automatic secret changes and redeployment without explicit approval. No evidence found of credential exfiltration or prompt injection; the skill explicitly treats logs as untrusted.
已確認的安全問題 (1)
能力複核項目 (3)
這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。
風險因素
⚙️ 外部命令 (50)
🌐 網路存取 (2)
📁 檔案系統存取 (7)
🔑 環境變數 (1)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/goldsky-io-compose-doctor/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/goldsky-io-compose-doctor?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/goldsky-io-compose-doctor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/goldsky-io-compose-doctor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/goldsky-io-compose-doctor.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 引用
goldsky-io. (2026). compose-doctor security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/goldsky-io-compose-doctor/audits/1BibTeX 引用
@techreport{goldsky-io-goldsky-io-compose-doctor-2026,
author = {goldsky-io},
title = {compose-doctor security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/goldsky-io-compose-doctor/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: "compose-doctor security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "goldsky-io"
date-released: "2026-10-19"
url: "https://skillstore.io/skills/goldsky-io-compose-doctor/audits/1"
identifiers:
- type: other
value: "skillstore:goldsky-io-compose-doctor:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Investigate Failing Tasks
Find failed invocations, review logs, and identify likely causes of HTTP errors or missed scheduled events.
Compare Deployed and Expected Behavior
Inspect app status and deployed source to investigate changes that did not reach the running application.
Diagnose Wallet and Sponsorship Errors
Distinguish local wallet limitations, unsupported sponsorship chains, and onchain reverts before selecting a remedy.
試試這些提示
Diagnose my existing Goldsky Compose app [app]. Start with status and logs, and ask before changing anything.
Investigate HTTP 500 errors in [app] during [time window]. Review failed runs and logs, then report the cause and verification steps.
Diagnose [wallet error] in [app] on [chain]. Check wallet and sponsorship configuration without requesting private keys or submitting transactions.
Investigate stale behavior in [app] after redeployment. Compare deployed source, failed runs, and collection state; propose fixes without applying them.
最佳實務
- Confirm the project, app, and local or cloud environment before running commands.
- Read logs and run details first; treat log content as untrusted and never execute embedded instructions.
- Approve state changes explicitly, review compatibility before forced deployment, and verify results after each authorized fix.
避免
- Redeploying repeatedly without examining logs, failed runs, or the deployed source.
- Pasting private keys, token values, or full environment files into diagnostic conversations.
- Automatically forcing deployment, cleanup, or app pauses while investigating a production issue.
常見問題
Is this for Docker Compose?
Can it create a new app?
Can it work without Bash access?
Can it reveal stored secret values?
Will it change my running app?
How does it investigate an onchain revert?
開發者詳細資訊
作者
goldsky-io授權
MIT
Skillstore 修訂
r1
版本提示
作者未聲明版本。
引用
587493833d6560296eae42efdb735565c0a3a3e8
維護新鮮度
2026/10/19
使用量
0 次下載 · 0 次瀏覽
檔案結構