Borrowing it
Nothing to install: this file belongs to ucsandman/DashClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ucsandman/DashClaw/main/.claude/skills/dashclaw-agent/troubleshoot/SKILL.mdgit clone --depth 1 https://github.com/ucsandman/DashClawWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ucsandman/dashclaw/troubleshoot)<a href="https://agentmods.dev/skills/ucsandman/dashclaw/troubleshoot"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw/troubleshoot.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.02324 |
| Opus 5 | $0.00009 | $0.01162 |
| Sonnet 5 | $0.00003 | $0.00465 |
| Haiku 4.5 | $0.00002 | $0.00232 |
Grade A, and why
troubleshoot scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Test with curl: Copies of this mod
1 near-identical copy found in the catalogue:
- troubleshoot — 89% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot DashClaw
Systematic diagnostics for common DashClaw errors, signal anomalies, and configuration issues.
Error Code Diagnostics
401 Unauthorized
Symptom: API calls return 401.
Checklist:
- Verify
x-api-keyheader is set (notAuthorization: Bearer) - Check
DASHCLAW_API_KEYenvironment variable is set - Confirm the key hasn't been rotated — API keys are shown once at creation
- Test with curl:
curl -H "x-api-key: $DASHCLAW_API_KEY" $DASHCLAW_BASE_URL/api/health
Root cause: DashClaw uses x-api-key header, not Bearer tokens. The middleware does timing-safe comparison first, then falls back to hash lookup.
403 Forbidden
Symptom: API calls return 403.
Checklist:
- Demo mode? Demo mode blocks all write operations. Check
DASHCLAW_MODEenv var. - Readonly key? Some keys are read-only. Check key permissions in dashboard.
- Guard blocking? If calling
/api/guardand getting 403, a policy is blocking the action — this is working as intended. - org_default trap? The
org_defaultorg blocks API access except onboarding routes. Create a real org first.
429 Rate Limited
Symptom: API calls return 429 Too Many Requests.
Defaults:
- Production: 100 requests/minute per IP
- Development: 1000 requests/minute per IP
Fixes:
- Set
DASHCLAW_DISABLE_RATE_LIMIT=truefor local development - For production: use
UPSTASH_REDIS_REST_URLfor distributed rate limiting - Batch operations where possible
503 Server Misconfigured
Symptom: API calls return 503.
Checklist:
- Is
DASHCLAW_API_KEYset? Missing key → 503 on protected routes - Is
DATABASE_URLvalid? Check connection string - Run health check:
curl $DASHCLAW_BASE_URL/api/health - Check the
/setuppage for readiness verification
Common Gotchas
| Gotcha | Explanation |
|---|---|
| Client-sent org headers stripped | Middleware ALWAYS strips x-org-id, x-org-role, x-user-id from requests. Org context comes from the API key, never the client. |
| Two thread systems | Context threads (ct_*) and message threads (mt_*) are separate systems. Don't mix them. |
| org_default blocks APIs | Users in org_default are blocked from most endpoints. Create or join a real org first. |
| API key shown once | Keys are displayed exactly once at creation. If lost, generate a new one. |
| 2MB body size limit | Request bodies larger than 2MB are rejected. |
| HTTPS required in production | Non-HTTPS connections are rejected in production mode. |
| Canonical JSON for signatures | Agent identity signatures require deterministic JSON key ordering. |
| Rate limiting is per-IP | Not per-key or per-agent. Multiple agents on same IP share the limit. |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 202 lines · 17 tokens per session scan A 90ef16225a98
troubleshoot is a skill published in the GitHub repository ucsandman/DashClaw (297 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,324 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-issue-solve
Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…