present-runbooks
Skill3 starsChanged 7 days agoApache-2.0View on GitHub
Open the native Ledgerly Runbooks canvas (numbered steps, track tabs, optional-feature checkboxes, Copy). Use when the user asks to open the runbook, open the runbooks, show the runbooks, present, walk the workshop, open the runbooks canvas, or go prompt-by-prompt. Do not open runbooks.html for those requests.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ledgerly/AGENTS.mdAGENTS.md
- ledgerly/.cursor/rules/disposable-demo-prs.mdcCursor rule
- ledgerly/.cursor/rules/ledgerly.mdcCursor rule
- ledgerly/.cursor/rules/multitask-no-wrapper.mdcCursor rule
- add-dashboard-widgetSkill
- choose-cursor-workflowSkill
- dispatch-subagentsSkill
- draft-collection-emailSkill
- hand-to-cloud-agentSkill
- reset-demo-stateSkill
- stage-linearSkill
- start-ledgerlySkill
- write-prisma-querySkill
- standard-bug-fixSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
If the user did not name 101, 201, 301, or 401, ask which track and wait.
- Very specific: line 16
Read ~/.cursor/skills-cursor/canvas/SKILL.md.
- Very specific: line 33
Start the server, seed, or run preflight-checker.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Present Runbooks
Open this canvas every time. Do not open runbooks.html. Do not start the app, seed, run preflight, or recap beats in chat.
1. Track
If the user did not name 101, 201, 301, or 401, ask which track and wait.
2. Copy and open the canvas
Read ~/.cursor/skills-cursor/canvas/SKILL.md. Read runbooks.canvas.tsx from this app root and write it with the file tool onto the workspace canvases path (overwrite if it exists):
/Users/<user>/.cursor/projects/<workspace>/canvases/runbooks.canvas.tsx
Then open that file (open_resource). Do not hand-edit the generated file. Do not embed HTML. Do not open runbooks.html.
The canvas is native cursor/canvas UI:
- Catalog tabs for
101/201/301/401(useCanvasStaterunbooks-track, default"101") - Numbered steps (
Step 1,Step 2, …) in one scrolling list under section headings. Numbers skip unchecked optional steps. - Optional-feature checkboxes on 301 (
runbooks-features), on by default - Copy on each prompt (
navigator.clipboard)
Tell the user to click the named track tab, uncheck optional features they are skipping, and scroll to the next step. Copy pastes the prompt.
3. Do not
- Start the server, seed, or run
preflight-checker. Those staystart-ledgerlyandpreflight-checker. - Recap beats, paste
PRESENTER.md, or add speaker notes in chat. - Open
runbooks.htmlor any other runbook view.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

