← Back to Skills Marketplace
346
Downloads
0
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install incident-triage-playbook
Description
Runbook-first incident triage workflow for service outages and high-error alerts.
README (SKILL.md)
Incident Triage Assistant
Use when an alert fires and you need a consistent first-15-min triage flow.
Inputs to Gather
- Primary target (service, team, or dataset)
- Current impact and urgency
- Assigned owner and deadline
Core Commands
triage intake --service \x3Cname> --severity \x3Csev>triage timeline --append "\x3Cevent>"triage owner --set "\x3Concall>"workflow checklist --from templates/checklist.mdworkflow report --from templates/report.md
Operating Notes
- Prefer explicit owner assignment before action.
- Keep timeline notes concise and timestamped.
- Save output artifacts for audit and handoff.
- This version adds a structured report template for post-task summaries.
Version marker: incident-triage-playbook 1.2.0
Usage Guidance
This package appears to be a lightweight incident triage playbook, but there are a few inconsistencies you should address before installing or using it: 1) Metadata mismatch — the package 'Name' field is '1.2.0' while SKILL.md identifies the skill as 'incident-triage-playbook'; ask the publisher for provenance or a proper homepage. 2) The runtime instructions call external CLI tools ('triage' and 'workflow') that are not provided or declared; ensure those tools exist in your agent environment or clarify how they are installed. 3) The healthcheck script echoes 'pipiwu-benchmark-alpha-skill' which looks like leftover text from another project — confirm this is not an accidental inclusion or sign of a copied/mispackaged bundle. If you proceed, run the skill in a restricted/sandboxed environment first, verify the origin, and do not grant any credentials or system-wide write access unless you confirm what the external CLIs do and trust their source.
Capability Analysis
Type: OpenClaw Skill
Name: incident-triage-playbook
Version: 1.2.0
The skill bundle provides a structured workflow and templates for incident triage. The scripts (echo-version.sh, healthcheck.sh) and markdown files (SKILL.md, templates/) contain no malicious logic, data exfiltration, or suspicious commands, and are fully aligned with the stated purpose of managing service outages.
Capability Assessment
Purpose & Capability
SKILL.md, templates, and the described runbook-first triage workflow are consistent with the stated purpose. However the package metadata 'Name: 1.2.0' (instead of a human-readable skill name) and the healthcheck script printing 'pipiwu-benchmark-alpha-skill' are misaligned with the incident-triage identity and look like copy/paste or release metadata errors. Also the instructions assume the presence of 'triage' and 'workflow' CLI commands but the skill does not declare required binaries or provide those tools.
Instruction Scope
SKILL.md directs the agent to run CLI commands (triage, workflow) and to use local templates — the templates are included so that's fine — but there is no install spec or declared required binaries for those CLI tools. The instructions do not attempt to read unrelated system files or exfiltrate data, but they give the agent discretion to 'Save output artifacts for audit and handoff' which could lead to unspecified persistence unless the agent environment policies restrict it.
Install Mechanism
This is instruction-only with no install spec. Included scripts are tiny and only echo strings. No downloads, no archives, and nothing is written to disk by an installer. From an install-mechanism point of view this is low risk.
Credentials
The skill requests no environment variables or credentials, which is proportionate. The only oddity is the healthcheck script printing a different skill name/version, which is inconsistent but not an immediate credential concern.
Persistence & Privilege
always:false and user-invocable:true (defaults) — the skill is not force-included and does not request elevated platform privileges. It does not modify other skills or request persistence; templates and small scripts are self-contained.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install incident-triage-playbook - After installation, invoke the skill by name or use
/incident-triage-playbook - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
incident-triage-playbook 1.2.0
- Added a structured incident report template (templates/report.md) for post-task summaries.
- Introduced the report workflow command (`workflow report --from templates/report.md`).
- Updated documentation to reflect new report workflow and template.
- Minor updates to scripts and banner for version alignment.
v1.1.0
Version 1.1.0 adds checklist support and operational improvements:
- Introduced an operations checklist template for structured handoffs (`templates/checklist.md`).
- Added a new command to run the checklist (`workflow checklist --from templates/checklist.md`).
- Updated documentation and banner to reflect new features.
- Minor script and healthcheck adjustments to support checklist functionality.
v1.0.0
Initial release of incident-triage-playbook.
- Provides a structured, runbook-driven workflow for incident triage.
- Supports clear input gathering: target, impact, owner, deadline.
- Core commands included for triage intake, timeline updates, and owner assignment.
- Emphasizes explicit ownership, concise timelines, and artifact retention.
- Designed for effective first 15 minutes of incident response.
Metadata
Frequently Asked Questions
What is 1.2.0?
Runbook-first incident triage workflow for service outages and high-error alerts. It is an AI Agent Skill for Claude Code / OpenClaw, with 346 downloads so far.
How do I install 1.2.0?
Run "/install incident-triage-playbook" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is 1.2.0 free?
Yes, 1.2.0 is completely free (open-source). You can download, install and use it at no cost.
Which platforms does 1.2.0 support?
1.2.0 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created 1.2.0?
It is built and maintained by Yikun Fu (@jiarani); the current version is v1.2.0.
More Skills