wizard
Generate an interactive bash wizard for steps only a human can perform. Invoke when the user asks for a script or wizard for manual setup: infrastructure provisioning, credentials or CI secrets, a third-party dashboard, or a one-off migration or cutover. Do not invoke for steps the agent can perform, or merely because the user mentions wizard, names a skill, or writes 'skill <word>'.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- wizard
- description
- Generate an interactive bash wizard for steps only a human can perform. Invoke when the user asks for a script or wizard for manual setup: infrastructure provisioning, credentials or CI secrets, a third-party dashboard, or a one-off migration or cutover. Do not invoke for steps the agent can perform, or merely because the user mentions wizard, names a skill, or writes 'skill <word>'.
- disable-model-invocation
- true
02 资源文件 1
- 脚本template.sh9.3 KB
03 SKILL.md 正文
Wizard
A wizard is a bash script that walks a human through a manual procedure. It opens each URL, states what to click and copy, captures values, writes them to their destination, confirms each stage, and shows the stages remaining.
template.sh owns the library: stage progress, confirmation gates,
URL opening, hidden secret entry, idempotent .env upserts, gh secret and
gh variable writes, and the closing summary. The agent authors only the
stages below the STAGES marker. Leave the library above it unchanged.
For each captured value, choose a destination: .env, a GitHub secret, a GitHub
variable, or no storage.
A wizard is ephemeral. Save it to a scratch path or scripts/, and commit it
only when the user asks for a repeatable setup path. Delete an ephemeral wizard
when its job is complete. For a retained setup script, link it from the README.
Procedure
- Scope the procedure.
- Read the repository first. For setup, read
.env*,README,docker-compose*, framework config, and.github/workflows/*; everysecrets.*andvars.*reference names a value the wizard needs to produce. For a migration, read the current state, the target state, and the irreversible actions between them. - Show the user the ordered stages and the values each produces. Apply the user's additions, removals, and reordering.
- Done when each stage is named in order and each captured value has a source, one destination, and a secret or public label.
- Read the repository first. For setup, read
- Map each stage's journey.
- Write the path a human follows: the URL, the action, where the value appears, and the variable it fills.
- When the current UI or command is unknown, check the docs or ask the user. Use verified steps rather than inventing them.
- Done when each stage has instructions a stranger can follow.
- Author the wizard.
- Copy
template.shto the target path. - Replace the example stage with one
stageper step, in dependency order, using the library helpers. SetTOTAL_STAGESto the stage count. - Open the URL before asking for its value. Use
ask_secretfor each secret value. Callwrite_envfor each persisted value. Callset_secretonly for values CI reads. Callconfirmbefore each irreversible action. - Keep each stage to one task, because each stage clears the screen.
- Done when every value from step 1 is captured and handled according to its chosen destination.
- Copy
- Verify and hand off.
- Run
bash -n <script>and, when installed,shellcheck <script>. - Run
chmod +x <script>. - Leave execution to the user: the wizard opens browsers and blocks on human
input. Trace it statically and check that each
set_secretname matches asecrets.*reference in CI. - Done when the checks pass and the user has the run command.
- Run
04 同仓库更多 Skills
writing-for-agents
Reference for writing documents an agent consumes: skills, AGENTS.md or CLAUDE.md, and docs reached by a pointer. Invoke when creating or editing a skill or an agent instruction file, or when a document's pointer wording, load, or structure is in question. Do not invoke merely because the user mentions writing-for-agents, names a skill, or writes 'skill <word>'.
wait-what
Stop and re-pitch the last message in plain, simplified language.
to-tickets
Split an agreed specification into reviewable vertical-slice issues with explicit blockers, then publish them after confirmation.
to-spec
Turn the current conversation into a specification and publish it after confirmation.
to-pr
Create a pull request from the current branch.
tdd
Test-driven development. Invoke only when the user asks to build a feature or fix a bug test-first, requests a red-green-refactor loop, or requests integration tests.