fai-incident-runbook-create — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited fai-incident-runbook-create (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Provide deterministic response steps for AI system incidents to reduce MTTR and communication chaos.
| Severity | Definition | Target Response |
|---|---|---|
| Sev0 | Full outage or critical harm risk | 15 min |
| Sev1 | Major degradation, high user impact | 30 min |
| Sev2 | Partial impact or workaround exists | 2 hours |
| Sev3 | Low impact | Next business day |
If safety violations exceed threshold:
- Enable kill switch for impacted AI feature.
- Route traffic to fallback model.
- Freeze deployments.
- Notify incident channel and on-call lead.Status Update
- Incident: <id>
- Severity: <sev>
- User impact: <summary>
- Mitigation in progress: <actions>
- Next update: <time>| Check | Pass Condition |
|---|---|
| Service restored | Core flows functional |
| Error rate normalized | Below alert threshold |
| Safety metrics stable | Within guardrail |
| Backlog processed | Queues drained |
| Issue | Cause | Fix |
|---|---|---|
| Repeated incidents | No preventive actions tracked | Add owners/dates and verify closure |
| Slow triage | Unclear severity mapping | Tighten severity matrix with examples |
| Conflicting updates | Multiple channels unmanaged | Define single source of truth channel |
# Example verification sequence
npm run lint
npm test
npm run build{
"quality_gate": {
"required": true,
"min_score": 0.8,
"block_on_failure": true
}
}| Control | Requirement |
|---|---|
| Secret handling | No plaintext secrets in repo |
| Access model | Least privilege role assignments |
| Logging | Redact sensitive data before persistence |
| Auditability | Keep immutable trace of critical actions |
| Symptom | Likely Cause | Recommended Action |
|---|---|---|
| Validation gate failures | Threshold too strict or wrong baseline | Recalibrate using a fixed reference dataset |
| Unexpected regressions | Missing scenario coverage | Add targeted regression tests and rerun |
| Production-only issues | Environment mismatch | Diff environment config and identity settings |
| Slow recovery during incidents | Unclear ownership/runbook steps | Add explicit owner and sequence in runbook |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.