wizard

Generate interactive bash wizards that walk humans through manual setup procedures.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill wizard-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wizard
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/wizard
Command: npx skills add https://github.com/falentio/cimi --skill wizard-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Some setup work—provisioning infrastructure, creating credentials, configuring CI secrets, navigating third-party dashboards—can only be done by a human, and re-explaining the same steps every time is tedious and error-prone. This Skill turns those manual procedures into a guided, step-by-step bash script that captures values and writes them where they belong. ## Core Features & Use Cases - Guided stage-by-stage scripts: Generates a bash wizard from a proven template with progress indicators, confirmation gates, cross-platform URL opening (including WSL), hidden secret entry, and idempotent .env upserts. - Credential and secret capture: Collects values from the human and writes them to .env files or GitHub Actions secrets and variables via gh. - Use Case: A project needs Stripe keys, a deploy token, and three CI secrets. The wizard opens each dashboard URL, tells the user exactly what to click and copy, stores the values in .env, sets the GitHub secrets, and prints a closing summary of everything configured. ## Quick Start Ask the agent to create a setup wizard that walks a human through configuring the project's environment variables and GitHub CI secrets.

Frequently Asked Questions about wizard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an interactive bash setup wizard?

Copy the provided template.sh, replace the example stage with one stage per manual step, and set TOTAL_STAGES to match. Use the built-in helpers like stage, open_url, ask, ask_secret, write_env, and set_secret without editing the library above the STAGES marker.

How to automate collecting API keys and CI secrets during project setup?

A generated wizard opens each provider's dashboard URL, prompts the human to paste values with hidden input for secrets, upserts them into .env, and pushes CI-needed values to GitHub Actions secrets using the gh CLI.

Does the wizard script work on WSL and macOS?

Yes, the open_url helper detects the platform and uses wslview, explorer.exe, xdg-open, or open as available. If no browser opener exists, it prints the URL for manual visiting.

What happens if the gh CLI is not available when setting GitHub secrets?

The set_secret and set_var helpers fall back to a warning and record the skipped item. The closing summary lists everything still to do by hand, including the exact gh command to run later.

When should I not use a setup wizard?

Do not use it for steps the agent can perform itself, since wizards exist only for human-only actions. Also avoid committing one-off wizards; they are ephemeral by default unless the team wants a repeatable setup path.