insforge-debug
Diagnose InsForge Backend Failures
InsForge failures can span logs, database state, policies, metrics, and deployments. This skill guides Claude, Codex, and Claude Code through evidence-based diagnosis.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "insforge-debug" from https://skillstore.io/skills/insforge-insforge-debug.md and its manifest at https://skillstore.io/api/skills/insforge-insforge-debug/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「insforge-debug」を使用しています。 A database request returns 403 for an authenticated user.
期待される結果:
- Primary route: inspect the PostgREST logs at the failure time.
- Verify the table policy role, USING expression, and WITH CHECK expression.
- Confirm that the configured JWT claim matches the policy helper.
「insforge-debug」を使用しています。 Several unrelated endpoints return intermittent 504 errors.
期待される結果:
The failures span subsystems, so check the platform incident report and correlate Postgres recovery events with the timeout window before concluding OOM.
「insforge-debug」を使用しています。 A frontend deployment reports an error.
期待される結果:
- Find the failed deployment and inspect its status metadata.
- Reproduce the build locally to obtain detailed output.
- Compare required environment variable keys with the deployment metadata.
セキュリティ監査
中リスクMost static alerts are Markdown syntax, example URLs, relative documentation links, or authorized troubleshooting steps. Confirmed risks involve unpinned CLI execution, privileged project inspection, infrastructure changes, and diagnostic data sent to InsForge services.
確認済みのセキュリティ上の懸念 (3)
機能レビュー項目 (47)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
🌐 ネットワークアクセス (2)
📁 ファイルシステムへのアクセス (1)
⚙️ 外部コマンド (50)
検出されたパターン
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/insforge-insforge-debug/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/insforge-insforge-debug?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/insforge-insforge-debug?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/insforge-insforge-debug/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/insforge-insforge-debug.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形式の引用
insforge. (2026). insforge-debug security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/insforge-insforge-debug/audits/5BibTeX形式の引用
@techreport{insforge-insforge-insforge-debug-2026,
author = {insforge},
title = {insforge-debug security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/insforge-insforge-debug/audits/5},
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: "insforge-debug security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "insforge"
date-released: "2026-08-31"
url: "https://skillstore.io/skills/insforge-insforge-debug/audits/5"
identifiers:
- type: other
value: "skillstore:insforge-insforge-debug:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Trace an API Failure
Map an SDK error or HTTP status to logs, database checks, policies, or metadata.
Investigate an Active Incident
Correlate resource pressure, gateway timeouts, database health, and service logs during an outage.
Run a Pre-Launch Audit
Review advisor findings, RLS coverage, auth settings, storage exposure, and performance indicators before release.
これらのプロンプトを試す
Diagnose this InsForge error: {error_message}. Identify the best evidence source, inspect it, and explain the likely cause.Investigate this InsForge access issue: {request_details}. Compare logs, RLS policies, metadata, and expected user claims before proposing a fix.Investigate {incident_window} for widespread InsForge latency or gateway failures. Correlate metrics, database health, logs, and platform incident evidence.Audit this InsForge project before launch. Prioritize critical advisor findings, then verify security, RLS, performance, health, metadata, and unresolved risks.
ベストプラクティス
- Start with the smallest diagnostic source that matches the observed symptom.
- Verify AI suggestions against logs, metrics, policies, metadata, or database state.
- Obtain explicit approval before commands that deploy, resize, modify data, or change billing.
回避
- Do not treat a single metric value as a root cause without trend and log correlation.
- Do not paste credentials, personal data, or unrestricted production logs into AI or feedback commands.
- Do not run service-role queries or infrastructure changes without confirming scope and authorization.