InsForge Debug

A symptom-driven playbook for diagnosing InsForge backend issues using logs, metrics, DB health, RLS policies, and the advisor.

Dev & CodingIntermediate★ 416⑂ 44AI score 8/10Last updated: Sep 4, 2026

What it does

Gives Claude a structured triage path for InsForge projects: which observability surface to query, in what order, and what to look for.

Debug primitive table: logs (5 backend sources), metrics (CPU/memory/disk), DB health (connections, slow queries, locks, index usage, cache hit), advisor (security/performance/health static scan), RLS policy dump, metadata, deploy state, and SDK error objects — each mapped to its real CLI command
Symptom recipes: SDK error envelopes, HTTP 4xx/5xx, RLS denials (loud 403 vs silent empty result), login/OAuth failures, edge function crashes, failed deploys, slow queries, 429s, 502/503/504 gateway timeouts, realtime channel problems
Proactive audits: pre-launch security/performance/health review with re-verification via isResolved
Upstream bug reporting: feedback command when the root cause is InsForge itself

All commands run through npx -y @insforge/cli; global installs are discouraged.

Who it's for

Developers building on the InsForge backend
Anyone who has lost hours to an RLS rule or a crash-looping edge function
Teams that need a pre-launch security and performance checklist

Examples

"My select returns an empty array" → the skill suspects silent RLS filtering, dumps db policies, then runs db query as service role to separate "filtered" from "no data"
"Intermittent 504s across unrelated paths" → it treats OOM as the leading hypothesis, correlates postgres.logs crash-recovery lines with the 5xx burst, and proposes an instance upgrade
"Audit before launch" → runs the advisor by severity and category, cross-checks with policies, metadata, and DB health, then re-scans after fixes

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/aiskillstore/marketplace/HEAD/pending/insforge/insforge-debug/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the pending/insforge/insforge-debug folder from the GitHub repo aiskillstore/marketplace into my ~/.claude/skills/insforge-debug/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/aiskillstore/marketplace.git /tmp/aiskillstore && mkdir -p ~/.claude/skills && cp -r /tmp/aiskillstore/pending/insforge/insforge-debug ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

Open a terminal.
Clone the repository: git clone https://github.com/aiskillstore/marketplace.git /tmp/aiskillstore
Create the skills folder: mkdir -p ~/.claude/skills
Copy the skill: cp -r /tmp/aiskillstore/pending/insforge/insforge-debug ~/.claude/skills/
Confirm the references/ folder came along: ls ~/.claude/skills/insforge-debug
Make sure Node.js is installed (node -v); the CLI runs on demand via npx -y @insforge/cli, no global install needed.
For advisor and incident features, log in first: npx -y @insforge/cli login
Restart Claude Code and ask something like "I'm getting a 403 from InsForge" to trigger the skill.

View source on GitHub ↗