incident-triage-and-pipeline-recovery — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited incident-triage-and-pipeline-recovery (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.
Use this skill when production behavior is already wrong and the team needs controlled recovery. It helps agents contain blast radius, diagnose quickly, restore trust, and avoid making the incident worse.
Do not jump to fixes before stabilizing the system and understanding impact.
Decide whether to:
Load mcp-data-observability-integration to inspect lag, run state, or Spark stage metrics before reruns or replays.
Identify:
Options include:
When replay or backfill is chosen, load safe-backfill-and-replay-orchestration and draft templates/backfill-plan.yaml before execution.
A fixed incident with no prevention work is unfinished.
Load skills/data-resiliency-testing-and-failure-injection/SKILL.md or references/data-resiliency-testing-patterns.md when the same failure mode must be prevented from surprising the team again.
| Rationalization | Reality |
|---|---|
| "Let us rerun everything now." | Blind reruns can duplicate data or destroy evidence. |
| "We can clean up downstream later." | Downstream trust loss is often harder to recover than the pipeline itself. |
| "The root cause can wait." | Without a guardrail, the same incident often returns quickly. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.