/reliability-report
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.
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill reliability-report --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/reliability-report
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
reliability-report.SKILL.mdname: 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.
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.
Repo: hoangsonww/Claude-Code-Agent-Monitor
Other skills on claude-code-agent-monitor.
- /debug-live-issue
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Open skill - /file-headers
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use automatically whenever writing a
Open skill - /mcp-operations
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.
Open skill - /repo-onboarding
Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and verification strategy before coding.
Open skill - /ship-feature
Implement a feature safely end-to-end in this repository. Use when adding or changing functionality across backend, frontend, or MCP with required verification and documentation updates.
Open skill - /update-project-docs
MANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to behavior, configuration, interfaces, events, schema, or features. Use automatically (without being asked) at the end of ANY change-set that adds
Open skill