Borrowing it
Nothing to install: this file belongs to whoamiTM/bi-mcp. 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/whoamiTM/bi-mcp/main/.claude/skills/bi-troubleshoot/SKILL.mdgit clone --depth 1 https://github.com/whoamiTM/bi-mcpWrote 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/whoamitm/bi-mcp/bi-troubleshoot)<a href="https://agentmods.dev/skills/whoamitm/bi-mcp/bi-troubleshoot"><img src="https://agentmods.dev/badge/skills/whoamitm/bi-mcp/bi-troubleshoot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/whoamitm/bi-mcp/bi-troubleshoot"><img src="https://agentmods.dev/badge/skills/whoamitm/bi-mcp/bi-troubleshoot.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00943 |
| Opus 5.5 | $0.00021 | $0.00377 |
| Sonnet 5.5 | $0.00011 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
bi-troubleshoot scanned grade A with 0 findings 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 2mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bi-troubleshoot — alert pipeline diagnosis
Use this when the user reports an alert problem on a specific camera — missing alerts, spurious alerts, wrong classification, alerts at the wrong times of day. Do NOT use for connectivity / PTZ / recording issues; those need different surfaces.
Step 1 — Confirm the symptom in data
bi_list_alerts(camera="<short>", limit=50)
Look at the time distribution, AI memo, and zone hits. Don't trust the user's framing alone — they may have miscounted, or the issue may be different from how they described it.
If they gave you a time range:
bi_list_alerts(camera="<short>", startdate=<unix>, enddate=<unix>, limit=200)
If you need clip context (was it recording? what resolution?):
bi_list_clips(camera="<short>", view="alerts", limit=20)
Step 2 — Read top-level config
bi_get_camera_config(short="<short>")
Note sense, contrast, recmode, aizones, profile/schedule flags.
The _note field tells you whether you got the admin (deep) or fallback
(shallow) view.
Step 3 — Drill into what camconfig doesn't expose
Pick the area that matches the symptom:
| Symptom | bi_get_reg key_path |
|---|---|
| Wrong AI classification / thresholds | AI\\<profile> (smartconf, smartlabels, smartzones) |
| Trigger zones look wrong | Motion\\<profile> (maskbits_*, objmaxpercent10) |
| Alerts not firing during PTZ preset | PTZ\\Presets (noalerts flag per preset) |
| Dahua IVS not reaching BI | camevents (ONVIF event handlers) |
| Wrong action (no email/webhook) | Alerts\\OnTrigger |
If bi_get_reg returns meta.stale: true, stop and ask the user to
re-export the camera before continuing — stale data will lead you astray.
Step 4 — Form ONE hypothesis
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.
- 2mo ago First seen · 110 lines · 53 tokens per session scan A 3a2e34675f7c
bi-troubleshoot is a skill published in the GitHub repository whoamiTM/bi-mcp (3 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 943 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…