sre-engineer

Fail

Audited by Runlayer on Mar 8, 2026

Risk Level: HIGH
Scan Summary
Max Score
92%
Files
6
Flagged
2
Chunks
10
Flagged Files (2)
sre-engineer/references/monitoring-alerting.mdHIGH
91.6%

Tool passed security scan

Risky tool definition detected

Description: - "Slow trends (address during business hours)" alert_routing: critical: - page: on-call engineer - slack: "#incidents" - create: incident doc warning: - slack: "#alerts" - ticket: auto-create if persists >1h info: - dashboard: only ```

sre-engineer/SKILL.mdMEDIUM
84.1%

Risky tool definition detected

Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning. license: MIT metadata: author: https://github.com/Jeffallan version: "1.1.0" domain: devops triggers: SRE, site reliability, SLO, SLI, error budget, incident management, chaos engineering, toil reduction, on-call, MTTR role: specialist scope: implementation output-format: code related-skills: devops-engineer, cloud-architect, kuber

Passed Files (4)Click to expand
sre-engineer/references/incident-chaos.mdOK
47.5%

Tool passed security scan

sre-engineer/references/error-budget-policy.mdOK
42.3%

Tool passed security scan

sre-engineer/references/automation-toil.mdOK
36.7%

Tool passed security scan

sre-engineer/references/slo-sli-management.mdOK
33.8%

Tool passed security scan

Audit Metadata
Max File Score
92%
Classification
KNOWN_SERVER_ALL_UNKNOWN
Files Scanned
6
Files Flagged
2
Chunks Analyzed
10
Analyzed
Mar 8, 2026, 09:47 AM
Security Audit — runlayer — sre-engineer