agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/skills/wizard/SKILL.md

wizard

Skill8 starsChanged 2 months agoMITView on GitHub

Generate an interactive bash wizard to guide humans through manual setup, dashboard, or credential steps. Use when setting up API keys, third-party dashboards, CI secrets, or infrastructure where human authentication is required — even if the user says \"create a setup wizard\". Do NOT use for steps the AI agent can execute autonomously.

  • Reads credentials

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 142 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    URL-First Navigation: Always open target URLs (open_url) before prompting the human for values or confirmation.

    line 16
  2. Very specific:

    Masked Secret Input: Use ask_secret for all API tokens, private keys, and passwords.

    line 17
  3. Very specific:

    Static Syntax Validation: Verify all generated wizard scripts with bash -n <script> and shellcheck before handing off to the user.

    line 18
  4. Very specific:

    Key Point: Do not touch the helper functions above the STAGES marker.

    line 53
  5. Very specific:

    Action: Run bash -n <script> and chmod +x <script>.

    line 57
  6. Distinctive:

    Key Point: Do not attempt to run the interactive wizard autonomously inside the agent session.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 142 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wizard

Generate structured, interactive Bash wizards that walk human operators step-by-step through manual dashboard procedures, secret provisioning, and irreversible cutover operations.

Core Invariants

  1. Human-Only Boundary: Wizards are strictly for tasks that require human interactive authentication, MFA, billing approval, or physical dashboard navigation.
  2. Immutable Helper Library: Preserve the standardized UI helper library in template.sh above the STAGES marker; never modify internal screen-clearing or secret-masking logic.
  3. URL-First Navigation: Always open target URLs (open_url) before prompting the human for values or confirmation.
  4. Masked Secret Input: Use ask_secret for all API tokens, private keys, and passwords; persist secrets directly to .env or GitHub Secrets (set_secret).
  5. Static Syntax Validation: Verify all generated wizard scripts with bash -n <script> and shellcheck before handing off to the user.

Architecture & Map of Content (MOC)

[ Manual Dashboard / Credential Prerequisite ] ──► [ Scope Stages & Target Secrets ] ──► [ Generate Wizard from template.sh ] ──► [ Operator Execution ]
ComponentResponsibilityReference Template
Bash Wizard EngineUI helpers, secret prompt, .env upsert, GitHub CLI writesskills/wizard/template.sh
Stage ScaffoldingLinear step sequence with URL triggersscripts/setup-*.sh
Verification PassBash syntax check and dry runbash -n <script>

Step-by-Step Procedure (TWI)

Step 1: Scope Manual Stages & Secrets Inventory

  • Action: Inspect .env.example, .github/workflows/*, and documentation to identify all manual inputs and secrets needed.
  • Key Point: For every value, determine: (1) Source URL / dashboard path, (2) Destination (.env, gh secret, or both), (3) Secret visibility.
  • Why: Thorough inventory prevents writing incomplete scripts that leave operators blocked midway.

Step 2: Map Operator Journey per Stage

  • Action: Draft clear, sequential instructions: which dashboard menu to click, where keys are generated, and which variable is populated.
  • Key Point: Clarify exact UI labels (e.g. "Settings $\rightarrow$ API Keys $\rightarrow$ Create Secret Key").
  • Inline Checklist:
    • Every stage maps to a single focused task
    • URLs verified against official documentation
    • Secret inputs mapped to ask_secret and write_env

Step 3: Author Wizard Script from template.sh

  • Action: Copy skills/wizard/template.sh to target path (e.g. scripts/setup-provider.sh), set TOTAL_STAGES, and author stages below the marker.
  • Key Point: Do not touch the helper functions above the STAGES marker.
  • Why: Consistency in UI helpers ensures uniform, robust terminal behavior across platforms (macOS, Linux, WSL).

Step 4: Validate Syntax & Deliver Hand-off

  • Action: Run bash -n <script> and chmod +x <script>. Provide the user with the exact execution command.
  • Key Point: Do not attempt to run the interactive wizard autonomously inside the agent session.
  • Why: The wizard requires interactive terminal input and browser windows that block autonomous agent subshells.

Anti-Rationalization Guardrails

Tempting RationalizationBinding RuleEngineering Rationale
"Generate a wizard for steps the agent could do via CLI."Execute agent-capable steps directly; reserve wizards for human-only tasks.Forcing humans to execute tasks an agent could run wastes human time.
"Prompt for secrets with standard read without masking."Mandatory ask_secret for all sensitive credentials.Plaintext secret prompts leak API tokens in terminal logs and shoulder surfing.
"Attempt to execute the interactive bash wizard in background subshell."Hand off wizard script to user with execution command.Background subshells hang indefinitely on interactive read and open calls.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free