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.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
테스트해 보기
"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 조회
파일 구조