data-observability-and-sla-management — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited data-observability-and-sla-management (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 the pipeline must be operated as a service, not just executed as code. It helps agents define what healthy looks like and how teams know when the system drifts away from that state.
Include:
Common signals:
Alerts should route to someone who can act, with enough context to investigate quickly.
Noisy alerts damage trust just as much as missing alerts.
Load references/data-resiliency-testing-patterns.md when the team must prove restart, retry, backlog, or failover behavior under controlled failure.
| Rationalization | Reality |
|---|---|
| "The scheduler already tells us if it fails." | Task failure alone does not measure stale, partial, or bad data. |
| "More alerts are safer." | Alert fatigue makes real incidents easier to miss. |
| "The business will tell us if something is wrong." | That means the system failed before the team noticed. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.