wizard

Use it when:: A setup needs steps only you can do, such as copying API keys from dashboards or adding CI secrets.
It does:: Writes a bash script that walks you through each step: opens the page, says what to click, saves what you paste.
You get:: A script that fills .env and GitHub secrets, with a progress count, confirmations and hidden entry for secrets.
Doesn't:: Run the script itself, or take over steps the agent could do on its own.

TL;DR

Here a wizard is an interactive bash script for a manual procedure that's tedious to do by hand and tedious to explain to an AI again: setting up a service, credentials or CI secrets, finding your way around a third-party dashboard, a one-off migration. The agent first reads the repo (.env.example, README, docker-compose, the secrets your GitHub workflows use) and shows you the stages in order, with the value each produces, for you to adjust. It then spells out each stage's path, such as "Dashboard → Developers → API keys → Reveal → copy", and asks you or checks the docs rather than invent a step it isn't sure of. A bundled template handles the experience: one stage per screen, how many are left, a confirmation before anything irreversible, opening links on any OS, and saving values to .env and GitHub secrets. The agent checks the syntax and reads the script through to confirm every value lands where it should, but doesn't run it, since that needs you. The script is meant for one run and then deleted, unless you want the setup repeatable and commit it.

Summarizes the skill at 5beb35b.

npx skills add https://github.com/mattpocock/skills --skill wizard

skills.sh page Source on GitHub All skills from mattpocock/skills

Total Downloads: 615,013 on skills.sh, Nov 9, 2026
Repo stars: 318,714 mattpocock/skills
First seen: Jun 29, 2026 on skills.sh

Weekly Downloads

27K

-21% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	34,314
Sep 28	30,866
Oct 5	30,913
Oct 12	44,498
Oct 19	37,150
Oct 26	32,039
Nov 2	28,988
Nov 9	26,973

Category	category:engineering category:software-engineering Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:command A one-shot action you invoke by name, such as turning the conversation into a PRD.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	infrastructure ci

SKILL.md

From mattpocock/skills at 5beb35b. Checked daily, last changed Oct 20, 2026.

Frontmatter

name: wizard
description: Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

Wizard

A wizard is a bash script that walks a human, step by step, through a manual procedure that's tedious to do by hand and tedious to re-explain to an AI every time. It opens each URL, says exactly what to click and copy, captures the values, writes them where they belong (.env, GitHub secrets), confirms at every stage, and shows how many stages are left. It might configure third-party services, run a one-off migration, or move the project from one state to another.

The delightful UX is already solved by template.sh: stage-by-stage progress, confirmation gates, cross-platform URL opening (including WSL), hidden secret entry, idempotent .env upserts, gh secret/gh variable writes, and a closing summary. Your job is only to scope the procedure and author its stages. The library above the STAGES marker is identical in every wizard; that consistency is the point: never hand-edit it.

A wizard is ephemeral by default: built for one run, saved to a scratch or scripts/ path, deleted when the job's done. Commit it only when the user wants a repeatable setup path that should live in the repo.

Process

1. Scope the procedure

Work out every manual step the human must take and every value that gets captured along the way. Read the repo first, don't ask cold:

For setup: .env, .env.example, .env.*, README, docker-compose*, framework config, and .github/workflows/* (every secrets.* / vars.* reference is a value the wizard must produce).
For a migration or transition: the current state, the target state, and the irreversible actions between them.

Then show the user the ordered list of stages and the values 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 (a) where the human gets it, (b) where it's written (.env, a GitHub secret, both, or nowhere; some stages are pure actions), and (c) whether it's secret (hidden entry) or public.

2. Map each stage's journey

For each stage, write the precise path a human follows: which URL to open, what to do there, where a value is shown, which variable it fills: e.g. "Dashboard → Developers → API keys → Reveal test key → copy". Where you don't actually know the current UI or the exact command, say so and ask the user or check the docs: never invent steps that may not exist.

Done when: every stage traces to concrete instructions a stranger could follow.

3. Author the wizard

Copy template.sh to the target path. Replace the example stage with one stage per step, in dependency order. Use the library helpers: stage, say/step, open_url, ask/ask_secret, write_env, set_secret/set_var, pause/confirm. Set TOTAL_STAGES to the number of stages you wrote.

Hold the bar the template sets: open the URL before asking for its value, use ask_secret for anything secret, write_env every persisted value, set_secret only the values CI actually needs, and confirm before any irreversible action. Each stage clears the screen so only the current step is visible: keep a stage to one focused task so nothing the human needs scrolls away. Don't touch the library above the marker.

4. Verify and hand off

bash -n <script>; run shellcheck if available.
chmod +x <script>.
Don't run it end-to-end yourself: it opens browsers and blocks on human input. Trace it statically instead: every value from step 1 is captured and lands where step 1 said, and every set_secret name exactly matches a secrets.* reference in CI.
Tell the user how to run it. If it's a repeatable setup path, commit it and link it from the README so the next person runs the script instead of asking an AI.