← ClaudeAtlas

wizardlisted

Generate an interactive bash wizard that walks a human through a manual procedure only they can perform — provisioning infrastructure, credentials and CI secrets, an unfamiliar third-party dashboard, a one-off migration or cutover. Use when the blocking work is manual and tedious to re-explain every time. NOT for a step an agent can perform itself.
konstantinos-malavazos/claude-code-playbook · ★ 2 · AI & Automation · score 68
Install: claude install-skill konstantinos-malavazos/claude-code-playbook
# Wizard — a script that walks the human through what only they can do It opens each URL, says exactly what to click and copy, captures the values, writes them where they belong, confirms at every stage, and shows how many stages are left. > Prior art: Matt Pocock's `wizard` skill (MIT). `template.sh` is included **verbatim**. This > file is a re-derivation that lands the script under the repo's own guardrails. ## The library is not yours to edit `template.sh` ships beside this skill and already solves the UX — stage progress, confirmation gates, cross-platform URL opening, hidden secret entry, idempotent `.env` upserts, `gh secret` / `gh variable` writes, a closing summary. Everything above the `STAGES` marker is identical in every wizard, and that sameness **is** the point. **Without `template.sh` this skill does nothing.** Install both files or neither. ## Scope it from the repo, not from the user Read before you ask. For setup: `.env`, `.env.example`, `.env.*`, the README, `docker-compose*`, framework config, and `.github/workflows/*`. **Every `secrets.*` and `vars.*` reference is a value the wizard must produce.** For a migration: the current state, the target state, and the irreversible actions between them. Then show the user the ordered stages and the value each produces, and confirm. They may add, drop or reorder. **Done when** every stage is named in order, and for each captured value you know where the human gets it, where it is written (`.env`, a CI secre