incident-report
incident-report is an Observability & incident response skill for AI agents, published by cardstack in the boxel repository on GitHub. Skillspace rates incident-report D (60/100) and it passed the safety scan; the rating is based on static analysis only.
Write up a production or staging incident (outage, degradation, 5xx / latency spike, indexing stall, task-recycle event) as a consistent, shareable report in the team's established house style — a slate-blue technical Artifact with a facts grid, stat tiles, a typed timeline, a trigger-vs-vulnerability root cause, a "ruled out" list, prioritized action items, and an evidence appendix. Use whenever asked to "create/write an incident report", "postmortem", "write this up for the team", or after investigating a deployed-environment incident and needing a deliverable others will read. Pairs with the aws-access, tail-logs, indexing-diagnostics, and prerender-sizing skills, which gather the evidence this report is built from.
- Grade
- D
- Quality
- 60 / 100
- Safety
- Passed
- GitHub stars
- 23
Unproven: rated by static analysis only, not yet compared head-to-head.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 93 / 100
- Maturity
- Basic: a single SKILL.md
- Security scan
- Low-risk patterns
- License
- MIT
- Adoption
- Adopted by 0 other repositories, in 0 collections
What the scanner flagged
- mentions secrets in text
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.