Wizard: Guide Human-Only Setup Steps

What it does

The skill starts by reading configuration and CI references to learn which values are actually required. It then proposes ordered stages, each with a known source, destination and secret classification. Its bundled template supplies progress, URL opening, hidden input and configuration helpers; the source says to leave the library above the stage marker intact. Verification is static because a real run opens browsers and waits for human input. The resulting script is temporary unless a repeatable setup path is explicitly wanted.

When to use it

• Guide a teammate through an unfamiliar provider dashboard.
• Collect only the credentials that existing CI jobs require.
• Prepare a manual migration checklist with explicit irreversible checkpoints.

Step-by-step workflow

1. Read project configuration and enumerate the manual actions and required values.
2. Confirm the ordered stages and each value’s source, destination and sensitivity.
3. Verify actual dashboard instructions against current documentation.
4. Author focused stages using the template’s existing helpers and confirmation gates.
5. Check Bash syntax, use shellcheck when available and hand execution to the human.

Example request

Use wizard to draft a human-operated setup procedure for our staging email provider. Read the existing environment example and CI workflow first. Map each required value to its documented dashboard location and destination. Hide secrets, exclude them from logs and commits, and include confirmation before irreversible changes. Show stages before writing the script. Verify statically; do not run the interactive procedure or request credentials in chat.

Worked example

If CI references only an email API token while the application also needs a public sender domain, the stage map should distinguish the two. The token belongs in the required secret store; the domain can be a normal variable. A copied dashboard path must be verified rather than guessed. Syntax checks catch malformed shell, while static tracing checks that every captured value reaches the intended destination. Neither check proves that a provider account was successfully configured.

What you get

A focused interactive setup script with reviewed stages and static validation results, ready for a human to run.

How to evaluate the result

• Trace each captured value to the correct destination.
• Check CI secret names match actual workflow references.
• Verify secret handling and irreversible-action confirmation without exposing values.

What you need

The bundled template, project configuration, current provider documentation and a human with account access. Bash and optional shellcheck are needed for validation.

Setup and activation

The publisher documents plugin setup for Claude Code, Codex and Copilot, and manual Agent Skills setup for Gemini CLI and other clients. Choose one distribution method per client to avoid duplicate skills. The engineering collection expects project-specific tracker, triage-label and document-location settings from setup-matt-pocock-skills. Keep referenced companion skills and files available. This catalogue review does not install or run them; scan the exact source before any later installation. Client tools, permissions and subagent support still need separate validation.

Limits and considerations

Hidden entry alone does not guarantee secure storage. Never expose secrets in chat, logs or commits; follow local credential-entry policy. The source forbids the authoring agent from running the full interactive flow. Destructive stages need explicit confirmation.

Related workflows

• Use handoff to give a human the setup context.
• Use retro when repeated manual setup reveals missing project documentation.

License and reuse

MIT at repository level (Copyright 2026 Matt Pocock). Preserve the copyright and permission notice when redistributing substantial source material; inspect any separately licensed dependencies or assets.

Further reading

• Reviewed SKILL.md (immutable commit)
• Publisher README: setup and compatibility
• Reviewed MIT license