Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.
Instructions your experts follow when using this skill.
Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.
If you see unfamiliar placeholders or need to check which tools are connected, see .
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.Files installed alongside these instructions.
Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".
Use to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
Use for the money side of a deal: the deal P&L, margin floors and discount bands, approval routing, the concession log, and the mix impact of a price change.