Claude
Skill
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.
Virus-scanned
Reviewed automatically before listing.
Download
hoangsonww-claude-code-agent-monitor-plugins_ccam-reports_skills_reliability-report-83d4df5.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-reports/skills/reliability-report
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install hoangsonww-claude-code-agent-monitor@llmmart
Git
git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole hoangsonww/claude-code-agent-monitor collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Reliability Report
- Confirm the review window and data scope.
- Read stats, analytics, recent events, alert history, and workflow error propagation.
- Separate:
- Active, waiting, completed, error, and abandoned sessions
- API errors, tool failures, interrupted turns, and stale data
- Trigger, impact, recovery, and remaining risk
- Compare
PreToolUseandPostToolUsecounts without assuming every gap is a failure. Check matching event context. - End with ranked corrective actions and the exact evidence needed for any unresolved hypothesis.
- Remain read-only.
Files (claude-code-agent-monitor)
-
agents
-
openai.yaml 274 B
interface: display_name: "Reliability Report" short_description: "Generate a CCAM reliability report from session outcomes,..." default_prompt: "Use $reliability-report to inspect CCAM data and complete this workflow safely." policy: allow_implicit_invocation: true
-
-
SKILL.md 864 B
--- 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.