$ loading_
Create or update repeatable operational runbooks and incident response procedures.
The material indicates this is an open-source, prompt-only runbook template that requires no secrets, declares no remote endpoints, and does not describe local execution or data access capabilities. Overall risk is low; the main caution is that its generated content may include manually provided operational commands and internal process details.
The material explicitly states that no keys or environment variables are required; the README also does not ask for login, tokens, or credential injection, so there is no direct credential collection, storage, or misuse surface evident.
No remote endpoints are declared, and the system flags it as prompt-only; the README only mentions actions 'if connectors are available,' but this skill itself does not define built-in outbound destinations or an exfiltration mechanism.
The material does not describe launching local processes, executing scripts, or invoking system capabilities; its function is to generate/update runbook documentation templates, not to execute the commands contained within them.
No permissions to read or write local files, databases, or other resources are declared; at most, it produces document content from user-provided information. If knowledge base/ITSM connectors are later attached, data access scope would depend on those external connectors rather than this skill's own description.
The source is an auditable open-source GitHub repository, and the system marks it as open-source, which is a meaningful risk-reducing factor. While the repo has 0 stars, no declared license, and unknown maintenance status, these introduce some trust uncertainty but are not enough to elevate it to high risk in the absence of closed-source behavior, malicious install steps, or suspicious injection signs.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "runbook" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/operations/skills/runbook/SKILL.md 2. Save it as ~/.claude/skills/runbook/SKILL.md 3. Reload skills and tell me it's ready
Create an operational runbook for our daily PostgreSQL backup task. Include prerequisites, execution steps, validation checks, common troubleshooting, rollback steps, and escalation conditions. Make the steps specific and include sample commands.
A clear database backup runbook with commands, checks, troubleshooting, and escalation paths.
Here is an existing service restart procedure. Please add missing troubleshooting steps, rollback actions, and escalation contacts, then rewrite it as a step-by-step runbook suitable for on-call operators: [paste existing procedure]
An improved service restart runbook with stronger failure handling, rollback actions, and escalation details.
Turn the following tribal knowledge about a weekly log cleanup task into a standard runbook. Use a consistent format and clearly document timing, step-by-step commands, success criteria, failure handling, and when to notify higher-level support: [paste scattered notes]
A standardized recurring-task runbook that converts scattered knowledge into repeatable documentation.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Create a step-by-step operational runbook for a recurring task or procedure.
/runbook $ARGUMENTS
## Runbook: [Task Name]
**Owner:** [Team/Person] | **Frequency:** [Daily/Weekly/Monthly/As Needed]
**Last Updated:** [Date] | **Last Run:** [Date]
### Purpose
[What this runbook accomplishes and when to use it]
### Prerequisites
- [ ] [Access or permission needed]
- [ ] [Tool or system required]
- [ ] [Data or input needed]
### Procedure
#### Step 1: [Name]
[Exact command, action, or instruction]
**Expected result:** [What should happen]
**If it fails:** [What to do]
#### Step 2: [Name]
[Exact command, action, or instruction]
**Expected result:** [What should happen]
**If it fails:** [What to do]
### Verification
- [ ] [How to confirm the task completed successfully]
- [ ] [What to check]
### Troubleshooting
| Symptom | Likely Cause | Fix |
|---------|-------------|-----|
| [What you see] | [Why] | [What to do] |
### Rollback
[How to undo this if something goes wrong]
### Escalation
| Situation | Contact | Method |
|-----------|---------|--------|
| [When to escalate] | [Who] | [How to reach them] |
### History
| Date | Run By | Notes |
|------|--------|-------|
| [Date] | [Person] | [Any issues or observations] |
If ~~knowledge base is connected:
If ~~ITSM is connected:
python sync.py --prod --dry-run from the ops server" is.Embed Zoom Virtual Agent chat on web with secure controls and context updates.
Quickly add Zoom’s prebuilt React video UI to web workflows.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Review an analysis for methodology, accuracy, bias, and evidence support.
Generate people analytics reports on headcount, attrition, diversity, and org health.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Catalogs runbook command options for easier lookup and reuse.
Write and maintain technical docs, from READMEs to API and runbook guides.
Plan actionable option proposals for runbook examples.
Connect to Runbook to manage documents and workflow processes efficiently.
Schedule and manage execution timing for operations tasks and workflows.
Search runbooks, detect gaps, draft docs, and analyze incident root causes.