About this skill

Problem

dashclaw-platform-intelligence is aimed at DashClaw platform operations, API integration, and security auditing. It addresses a practical issue: documentation, repository snapshots, and the running instance can drift. When an engineer needs to answer questions such as 'which API routes exist now?', 'is this environment variable required?', or 'what is the current schema?', relying on a static SKILL.md may produce stale results. The skill ranks evidence sources: live query first, then the running instance's /api/doctor, then generated repository files, and finally the snapshot.

How It Works

Prefer live queries: when available, query the platform first for current routes, env vars, and schema, rather than treating the snapshot as latest truth.
Fall back to doctor: in OpenClaw or the Claude app, if python -m livingcode, the livingcode package, or a repository checkout is unavailable, use GET {baseUrl}/api/doctor for live route/shape health. The call requires x-api-key and may return 401/403 without it.
Read generated static files: if the repository is reachable, inspect app/lib/doctor/generated/shape.json and docs/api-inventory.json. These are regenerated by the repository refresh flow and track the same facts.
Use the snapshot last: if neither API nor repository is reachable, treat the SKILL.md snapshot as the best available source. It covers 226 API routes, 57 categories, 4 required variables, 137 optional variables, and 89 tables, including DASHCLAW_API_KEY, DATABASE_URL, ENCRYPTION_KEY, and NEXTAUTH_SECRET.

Boundaries and Caveats

This skill is useful for DashClaw API inventory review, environment variable checks, route health checks, and locating security/compliance endpoints when a repo checkout is unavailable. It is not a substitute for pre-release verification of live behavior, permissions, or schema. If the live endpoint and the snapshot disagree, trust the live query.

Screenshots

Use Cases

Check live DashClaw routes before relying on stale docs by querying live or /api/doctor.
Verify required variables like DASHCLAW_API_KEY and DATABASE_URL before deployment.
In Claude app without a repo checkout, confirm tables or route categories from the shape snapshot.
Locate security, compliance, and webhook endpoints in the API inventory and verify health via doctor.

Best For

Platform engineers handling DashClaw deployment incidents who need live route and env var confirmation.
Backend engineers integrating DashClaw APIs who need to locate actions, capabilities, and webhook endpoints.
Security and compliance auditors who need to verify security, compliance, and evidence export endpoints.
AI assistant developers working in Claude app who need doctor fallback queries without a repo checkout.