When you've got a concrete error in an InsForge project (SDK error, 4xx/5xx response, failing edge function, broken auth flow), this skill walks you through the diagnostic commands to pinpoint the cause. The fastest path is `diagnose --ai` with your error message, which inspects backend state and returns both diagnosis and suggested fixes. If you want more control, the manual scenarios map symptoms to specific log sources and health checks: PostgREST logs for PGRST errors, database connection checks for timeouts, function logs for 502s. One thing to know: 429 rate limits aren't logged backend-side, so you'll need to audit client-side request patterns instead. For proactive health audits without a specific failing request, use insforge-backend-advisor instead.
npx -y skills add insforge/agent-skills --skill insforge-debug --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills
moizibnyousaf/ai-agent-skills
github/awesome-copilot