Individual 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.
plugins/ccam-reports/skills/reliability-report/SKILL.md
Source commit 14907bd6420bae80ddc01d0b7cd657980f0cf2d0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,171
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-agents Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- express Repository topic
- expressjs Repository topic
- node Repository topic
- nodejs Repository topic
- python Repository topic
- react Repository topic
- rest-api Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 864 bytesagents/openai.yamlasset · 274 bytes
Read excerpt
# 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.