reliability-report — Claude Code skill: report and install
This skill reviews CCAM session outcomes, hook events, alerts, and tool failures to produce a reliability report. Use it for health reviews or incident follow-up.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a claude-codeWhat reliability-report does
The skill starts by establishing the review period and data scope. It then checks statistics, analytics, recent events, alert history, and how workflow errors propagate. Its report separates session states from API and tool errors, interrupted turns, and stale data, then tracks each issue through trigger, impact, and recovery.
It compares PreToolUse and PostToolUse counts alongside matching event context, so a count mismatch alone does not become a failure claim. The report closes with ranked corrective actions and the evidence needed to test unresolved hypotheses. It is read-only, so it does not alter the monitored data.
What it helps with
- summarize session outcomes for a chosen review window
- trace API errors, tool failures, and interrupted turns
- audit hook delivery by comparing
PreToolUseandPostToolUseevents - rank corrective actions and specify evidence for open hypotheses
Example prompts for the agent
- Prepare a CCAM reliability report for the selected period and identify the main failures.
- Audit hook delivery by comparing
PreToolUseandPostToolUseevents with their context. - Review recent errors and rank corrective actions, including evidence needed to test open hypotheses.
How to install reliability-report
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a claude-code2Manually: put the files in place
~/.claude/skills/reliability-report/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/reliability-report/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a codex2Manually: put the files in place
.agents/skills/reliability-report/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a cursor2Manually: put the files in place
.cursor/skills/reliability-report/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hoangsonww/Claude-Code-Agent-Monitor reliability-report2Manually: put the files in place
.github/skills/reliability-report/SKILL.md1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a gemini-cli2Platform CLI
gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor --path plugins/ccam-reports/skills/reliability-reportManually: put the files in place
.devin/skills/reliability-report/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about reliability-report
How do I install reliability-report in Claude Code?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report -a claude-code, then open ~/.claude/skills/reliability-report/SKILL.md.
What does reliability-report do?
It reviews sessions, hook events, alerts, tool failures, and data freshness, then reports causes, impact, recovery, and ranked corrective actions.
Which platforms support reliability-report?
The skill is listed for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
Source text
SKILL.md · MIT
--- name: reliability-report description: > Generate a CCAM reliability report from session outcomes, hook events, alerts, tool failures, and data freshness. Use for health reviews, incident follow-up, hook-delivery audits, or reliability trend summaries. --- # Reliability Report 1. Confirm the review window and data scope. 2. Read stats, analytics, recent events, alert history, and workflow error propagation. 3. Separate: - Active, waiting, completed, error, and abandoned sessions - API errors, tool failures, interrupted turns, and stale data - Trigger, impact, recovery, and remaining risk 4. Compare `PreToolUse` and `PostToolUse` counts without assuming every gap is a failure. Check matching event context. 5. End with ranked corrective actions and the exact evidence needed for any unresolved hypothesis. 6. Remain read-only.
© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor