← 返回 Skills 市场
solomonneas

S³ Incident Runbook Templates

作者 Solomon Neas · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
204
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install s3-incident-runbooks
功能描述
Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to...
安全使用建议
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).
功能分析
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.
能力评估
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.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install s3-incident-runbooks
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /s3-incident-runbooks 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
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.
元数据
Slug s3-incident-runbooks
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

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... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 204 次。

如何安装 S³ Incident Runbook Templates?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install s3-incident-runbooks」即可一键安装,无需额外配置。

S³ Incident Runbook Templates 是免费的吗?

是的,S³ Incident Runbook Templates 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

S³ Incident Runbook Templates 支持哪些平台?

S³ Incident Runbook Templates 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 S³ Incident Runbook Templates?

由 Solomon Neas(@solomonneas)开发并维护,当前版本 v1.0.0。

💬 留言讨论