turbo-doctor
Diagnose Goldsky Turbo Pipeline Failures
Goldsky Turbo pipeline failures can interrupt data delivery and require careful investigation. This skill guides status checks, log analysis, and repair recommendations with confirmation before changes.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "turbo-doctor" from https://skillstore.io/skills/goldsky-io-turbo-doctor.md and its manifest at https://skillstore.io/api/skills/goldsky-io-turbo-doctor/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「turbo-doctor」を使用しています。 Illustrative scenario: my pipeline is paused and no new records are arriving.
期待される結果:
- Status: Paused.
- Issue: Data delivery is interrupted while the pipeline is paused.
- Evidence: The supplied pipeline listing reports a paused state.
- Recommended fix: Confirm the pipeline is not job-mode and ask whether to resume it.
- Prevention: Check pipeline status after planned maintenance.
「turbo-doctor」を使用しています。 Illustrative scenario: my pipeline reports authentication errors, and its referenced secret is absent from the secret listing.
期待される結果:
- Issue: The pipeline cannot authenticate to its destination.
- Likely cause: The required secret is missing, based on the supplied configuration and secret listing.
- Recommended fix: Confirm credential creation and enter the value through the CLI prompt.
- Verification: Recheck status and logs after the approved repair.
- Prevention: Verify required secrets exist before deployment.
セキュリティ監査
安全All 23 static findings are false positives: Markdown formatting, routine diagnostics, or repair commands explicitly gated by user confirmation. Destructive actions require approval, and credential guidance avoids inline values and disclosure in conversation. No evidence found of prompt injection, unauthorized exfiltration, or malicious reconnaissance in the reviewed files.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/goldsky-io-turbo-doctor/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/goldsky-io-turbo-doctor?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/goldsky-io-turbo-doctor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/goldsky-io-turbo-doctor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/goldsky-io-turbo-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). turbo-doctor security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/goldsky-io-turbo-doctor/audits/1BibTeX形式の引用
@techreport{goldsky-io-goldsky-io-turbo-doctor-2026,
author = {goldsky-io},
title = {turbo-doctor security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/goldsky-io-turbo-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: "turbo-doctor security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "goldsky-io"
date-released: "2026-09-28"
url: "https://skillstore.io/skills/goldsky-io-turbo-doctor/audits/1"
identifiers:
- type: other
value: "skillstore:goldsky-io-turbo-doctor:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Investigate Interrupted Data Delivery
Inspect status and recent logs for an existing pipeline that stopped delivering records, then review the proposed repair.
Triage Pipeline Incidents
Investigate pipelines in error or prolonged starting states and gather evidence before approving operational changes.
Diagnose Through Shared Command Output
Follow reference-mode diagnostic commands and share sanitized results when the assistant cannot access a shell.
これらのプロンプトを試す
My existing Goldsky Turbo pipeline [name] is in error state. Check its status and recent logs, explain the evidence, and ask before changes.
Pipeline [name] is running, but expected records are missing. Inspect recent logs and compare expected behavior with observed results. Do not change anything yet.
Use reference mode to diagnose pipeline [name], which has connection errors. Give me diagnostic commands and analyze the sanitized outputs I provide.
Diagnose failed job-mode pipeline [name] using status, logs, and available YAML. Explain recovery risks and request explicit confirmation before deletion or redeployment.
ベストプラクティス
- Confirm the current project and target pipeline before diagnosing or approving changes.
- Use recent status and log evidence, and redact credentials before sharing diagnostic output.
- Review destructive repair risks and explicitly approve changes before execution.
回避
- Requesting a new pipeline or a standalone CLI reference instead of diagnosing an existing problem.
- Clearing state or deleting a pipeline without reviewing impact and confirming the action.
- Pasting secret values into chat or passing credentials inline in shell commands.
よくある質問
Which problems does this skill investigate?
Can it work without shell access?
Does it make changes automatically?
How does it handle credentials?
Can it restart job-mode pipelines?
Does it build new pipelines?
開発者情報
作成者
goldsky-ioライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1
メンテナンスの新しさ
2026/9/30
利用状況
0 ダウンロード · 0 閲覧
ファイル構成