runbooklisted

Build or refresh a repo's operational runbook by mining all available context — project code, agent memory, past sessions, and local CLAUDE.md/.claude rules. Use for "create the runbook", "build the runbook for this repo", "generate runbook", or the first time a skill needs a runbook that doesn't exist yet.
danielimad/SKILLS · ★ 0 · AI & Automation · score 54

Install: claude install-skill danielimad/SKILLS

# Runbook — generate the per-repo operational card Produces `.docs/runbook.md` (or the docs folder this repo already uses — the runbook itself is what names that path for every other skill): the one card that carries everything project-shaped (IDs, tenants, checklists, deploy and git rules) so every other skill reads it instead of re-asking. This is the harvester that fills that card from context that already exists about the repo. ## Sources to mine (in order — each fills part of the card) 1. **The repo itself** — package manifests (stack, package manager, scripts), `.env.example` / env key NAMES (never values), supabase/wrangler/vercel config, migrations, routes/edge functions, deploy scripts, CI. This is ground truth. 2. **Local Claude rules** — the repo's `CLAUDE.md`, `.claude/settings.json`, `.claude/settings.local.json`, `AGENTS.md`, `.agents/`. Pull repo-specific bans/identity (e.g. git/GitHub bans, committer identity, protected files, forbidden actions) straight into the card's git/deploy rules. 3. **Existing repo docs** — architecture.md, decisions.md, integrations.md, any domain docs. Don't duplicate them; extract the operational facts (test tenants, IDs, deploy commands) into the runbook and cross-link. 4. **Agent memory** — whatever persistent memory your setup keeps for this project (e.g. `~/.claude/projects/<slug>/memory/`, or a memory MCP server). Mine recurring IDs, test accounts, known gotchas, deploy quirks. 5. **Past sessions** — the repo's transcripts (e