SRE & Incident Management Platform
v1.0.0Comprehensive SRE platform enabling SLO definition, reliability assessment, incident response, chaos engineering, and error budget management without externa...
⭐ 2· 641·1 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description promise a methodology and runbook/templates for SRE tasks. The skill is instruction-only with no required binaries, env vars, or installs, which is proportionate for a documentation/template-style skill.
Instruction Scope
SKILL.md contains templates, assessment checklists, SLI/SLO guidance, runbooks, and policy examples. The instructions do not direct the agent to read system files, request secrets, or call external endpoints. Note: some templates describe 'automated escalation' or 'automated detection' as patterns — those are prescriptive examples, not executable code; if you give your agent other connectors or credentials, it could use those templates to take action, but the skill itself does not perform I/O.
Install Mechanism
No install spec and no code files. Instruction-only skills write nothing to disk and carry low install risk.
Credentials
The skill requests no environment variables, credentials, or config paths. There is no disproportionate access requested relative to the stated purpose.
Persistence & Privilege
Flags: always=false and normal model invocation allowed. The skill does not request permanent presence or modification of other skills or system-wide settings.
Assessment
This is essentially a documentation/template skill — it looks coherent and low-risk. Before installing: (1) remember it provides methodology only; it won’t automatically run your incident tooling unless you give the agent other connectors or credentials; (2) don’t paste sensitive production config or credentials into prompts when using the templates; (3) verify any external links (paid context packs) separately and avoid entering payment/credential info into the skill itself; (4) if you later connect automation (CI, monitoring, chatops), review those connectors’ permissions because the templates could be used to drive actions when combined with other skills or integrations.Like a lobster shell, security has layers — review code before you run it.
chaosvk977e7jj2av4acqj9dz38dmgas81azmpdevopsvk977e7jj2av4acqj9dz38dmgas81azmpincidentvk977e7jj2av4acqj9dz38dmgas81azmplatestvk977e7jj2av4acqj9dz38dmgas81azmpmonitoringvk977e7jj2av4acqj9dz38dmgas81azmponcallvk977e7jj2av4acqj9dz38dmgas81azmppostmortemvk977e7jj2av4acqj9dz38dmgas81azmpreliabilityvk977e7jj2av4acqj9dz38dmgas81azmpslovk977e7jj2av4acqj9dz38dmgas81azmpsrevk977e7jj2av4acqj9dz38dmgas81azmp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.