Write a runbook
Turn a task someone does by hand into a runbook: exact steps and commands, a check after each, what to do when one fails, and how to undo it.
In Lobstack: Skills › Library › Add
What your agent will do.
A procedure lives in one person's head or an old chat thread — a deploy, a restore, a month-end job, rotating a key — and someone else needs to be able to do it.
- 01
Get the procedure from its source: the person, the chat history, the shell history, old notes. Ask what it is for and how often it runs.
- 02
List what is needed before starting: access, tools, versions, and who must be told.
- 03
Write each step as one action with the exact command or click path. Not "configure the server" — which setting, set to what.
- 04
After each step, add the check that proves it worked and what the output should look like.
- 05
Run every read-only command yourself to confirm it works as written. Never run a step that changes anything; mark those "(not run)".
- 06
For each step that can fail, say what failure looks like and what to do. End with how to undo the whole thing, and when to stop and call someone.
- 07
Post it as a document. Ask before saving it to a shared wiki or Notion.
A runbook is done when someone who has never done the task could follow it at 2am without asking anyone.
The whole SKILL.md: 33 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: runbookdescription: "Turn a task someone does by hand into a runbook: exact steps and commands, a check after each, what to do when one fails, and how to undo it."metadata: title: "Write a runbook" category: operations tags: [runbooks, procedures]--- ## When to use this A procedure lives in one person's head or an old chat thread -- a deploy, arestore, a month-end job, rotating a key -- and someone else needs to be able todo it. ## How 1. Get the procedure from its source: the person, the chat history, the shell history, old notes. Ask what it is for and how often it runs.2. List what is needed before starting: access, tools, versions, and who must be told.3. Write each step as one action with the exact command or click path. Not "configure the server" -- which setting, set to what.4. After each step, add the check that proves it worked and what the output should look like.5. Run every read-only command yourself to confirm it works as written. Never run a step that changes anything; mark those "(not run)".6. For each step that can fail, say what failure looks like and what to do. End with how to undo the whole thing, and when to stop and call someone.7. Post it as a document. Ask before saving it to a shared wiki or Notion. A runbook is done when someone who has never done the task could follow it at2am without asking anyone.
- OperationsFeatured
Weekly status report
Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.
SKILL.md · App - Operations
Spreadsheet cleanup
Clean a messy spreadsheet or CSV (headers, types, duplicates, blanks, inconsistent values) into a tidy copy, with a log of every change.
SKILL.md · App - Operations
Onboarding guide
Write an onboarding guide for someone new from the existing docs, repos and chat: day-one setup, who to ask, and a first real task.
SKILL.md · App - Operations
Scheduled check
Run a named checklist on a schedule, compare with the last run, and report only what changed or failed. Never fixes anything on its own.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App