← Back to Skills Marketplace
S³ Incident Runbook Templates
by
Solomon Neas
· GitHub ↗
· v1.0.0
· MIT-0
204
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install s3-incident-runbooks
Description
Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to...
Usage Guidance
This skill is coherent for building incident runbooks, but treat it as a recipe for human operators rather than something to run automatically. Before installing or letting an agent execute these instructions: 1) Do not provide DB or cloud credentials to the skill; supply examples or redact secrets. 2) Require explicit human confirmation for any destructive command (rollbacks, pg_terminate_backend, kubectl apply/scale). 3) Limit the agent's execution environment and Kubernetes/DB permissions (use least privilege, test in staging). 4) Verify and replace placeholder internal endpoints (api.company.com, prometheus, grafana, sentry) with your real URLs or remove them. 5) Have on-call/infrastructure owners review and approve the runbook steps and any referenced scripts (resources/implementation-playbook.md appears referenced but not included). If you need the agent to perform actions, consider adding stricter guards (declared required env vars, explicit confirmation prompts, and scoped short-lived credentials).
Capability Analysis
Type: OpenClaw Skill
Name: s3-incident-runbooks
Version: 1.0.0
The skill bundle provides standard incident response templates and runbooks for service outages and database issues. It contains common DevOps commands (kubectl, psql, curl) and SQL queries intended for troubleshooting and mitigation during production incidents. The content is clearly aligned with its stated purpose, and no evidence of data exfiltration, malicious execution, or prompt injection was found in SKILL.md or _meta.json.
Capability Assessment
Purpose & Capability
Name and description match the contents: templates and step-by-step operational runbooks for incident response. The commands and sections (kubectl, psql, curl, rollout undo, scaling, network policy) are plausible and expected in an on-call/infrastructure runbook. However, some items (internal endpoints, Sentry/Grafana links, feature-flag APIs) are placeholder/organization-specific and the SKILL.md assumes access to internal infrastructure without declaring those needs.
Instruction Scope
The instructions include concrete, executable commands (kubectl, psql, curl, kubectl apply, pg_terminate_backend, rollout undo, scaling) that would perform destructive or high-privilege actions if executed. They reference environment variables ($DB_HOST, $DB_USER) and internal endpoints (api.company.com, prometheus, grafana, sentry) that are not declared in requires.env. The skill also suggests applying network policies and terminating DB backends — actions beyond mere read-only diagnostics. Because SKILL.md could be used to drive an agent to run these commands, the lack of explicit guardrails (explicitly requiring human confirmation or declaring that commands are examples only) is a concern.
Install Mechanism
Instruction-only skill (no install spec, no code files). This minimizes disk/installation risk because nothing is written or downloaded by the skill itself.
Credentials
The skill declares no required environment variables or credentials but the runbooks reference sensitive values and services (DB_HOST, DB_USER, internal API endpoints, PagerDuty/Slack/Pager integrations, psql auth). That mismatch means the instructions assume access to secrets and internal systems without declaring or justifying them. Users should not supply full DB or cloud credentials to this skill without strict controls.
Persistence & Privilege
The skill is not always-enabled and doesn't request persistent privileges or modify other skills. However, it instructs high-privilege operational steps; combined with the platform default that the agent can invoke the skill autonomously, this increases the blast radius if the agent is permitted to execute commands. There are no special install-time persistence concerns.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install s3-incident-runbooks - After installation, invoke the skill by name or use
/s3-incident-runbooks - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of structured runbook templates for incident response.
- Provides templates for incident response covering detection, triage, mitigation, and resolution.
- Includes clear instructions on when and how to use the skill.
- Defines incident severity levels and a standardized runbook structure.
- Offers an in-depth service outage runbook template with actionable steps, escalation matrices, and communication guidance.
- Suitable for building and operating production-quality incident runbooks and onboarding on-call engineers.
Metadata
Frequently Asked Questions
What is S³ Incident Runbook Templates?
Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to... It is an AI Agent Skill for Claude Code / OpenClaw, with 204 downloads so far.
How do I install S³ Incident Runbook Templates?
Run "/install s3-incident-runbooks" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is S³ Incident Runbook Templates free?
Yes, S³ Incident Runbook Templates is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does S³ Incident Runbook Templates support?
S³ Incident Runbook Templates is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created S³ Incident Runbook Templates?
It is built and maintained by Solomon Neas (@solomonneas); the current version is v1.0.0.
More Skills