Nuget Trusted Publishing
dotnet/skills
Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens.
Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each…
Install Wizard
$ npx skills add smontlouis/bible-strong --skill wizard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install smontlouis/bible-strong wizard --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/smontlouis/bible-strong.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/wizard .claude/skills/wizard && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wizard" agent skill from https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizard into .claude/skills/wizard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wizard", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add smontlouis/bible-strong --skill wizard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install smontlouis/bible-strong wizard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smontlouis/bible-strong.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/wizard .agents/skills/wizard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wizard" agent skill from https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizard into .agents/skills/wizard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wizard", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add smontlouis/bible-strong --skill wizard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install smontlouis/bible-strong wizard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smontlouis/bible-strong.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/wizard .cursor/skills/wizard && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wizard" agent skill from https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizard into .cursor/skills/wizard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wizard", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/smontlouis/bible-strong.git --path .agents/skills/wizard--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add smontlouis/bible-strong --skill wizard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install smontlouis/bible-strong wizard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smontlouis/bible-strong.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/wizard .gemini/skills/wizard && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wizard" agent skill from https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizard into .gemini/skills/wizard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wizard", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install smontlouis/bible-strong wizardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add smontlouis/bible-strong --skill wizard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/smontlouis/bible-strong.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/wizard .github/skills/wizard && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wizard" agent skill from https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizard into .github/skills/wizard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wizard", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add smontlouis/bible-strong --skill wizard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install smontlouis/bible-strong wizard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/smontlouis/bible-strong.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/wizard .opencode/skills/wizard && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wizard" agent skill from https://github.com/smontlouis/bible-strong/tree/master/.agents/skills/wizard into .opencode/skills/wizard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wizard", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wizard- GitHub stars
- 171
- Used in
- 1 other repo
- Token cost
- ~1k tokens
- SKILL.md length
- 608 words
- Files
- 2
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each…
- Works in 4 steps: Scope the procedure → Map each stage's journey → Author the wizard → …
- Tasks that involve CI/CD
- Runs Shell scripts from its folder; calls gh and bash
What it does
Wizard is an agent skill from smontlouis/bible-strong. Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `template.sh`).
It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions and Bash. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve CI/CD
Example prompts
- “/wizard”
Requirements
- A Bash shell
- Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1dfaa0d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Shell), which the agent can run.
Shell commands in SKILL.md call:
ghbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wizard loads about 1k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 608 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:3
alues, confirming each step, and writing .env files and GitHub Actions secrets. - NoteMentions a .env fileSKILL.md:9
values, writes them where they belong (`.env`, GitHub secrets), confirms at every stage, and shows how much is left. It - NoteMentions a .env fileSKILL.md:11
g WSL), hidden secret entry, idempotent `.env` upserts, `gh secret`/`gh variable` writes, and a closing summary. **Your - NoteMentions a .env fileSKILL.md:21
- For setup: `.env`, `.env.example`, `.env.*`, `README`, `docker-compose*`, framework config, and `.github/workflows/*` - NoteMentions a .env fileSKILL.md:26
human gets it, (b) where it's written (`.env`, a GitHub secret, both, or nowhere — some stages are pure actions), and (
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from smontlouis/bible-strong at commit 1dfaa0d, republished under its GPL-3.0 licence (© smontlouis). 608 words, ~1,037 tokens.
Download SKILL.mdSave it as
.claude/skills/wizard/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- wizard
- description
- Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.
- disable-model-invocation
- true
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 much is 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 — progress with time-remaining, 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/*(everysecrets.*/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.
Show full SKILL.md (204 more words)Show less
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 — and set TOTAL_STAGES and TOTAL_MINUTES to honest estimates (this drives the time-remaining display).
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>; runshellcheckif 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_secretname exactly matches asecrets.*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.
© smontlouis, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/wizard of smontlouis/bible-strong.
- SKILL.md
- template.sh
Open the folder on GitHubat commit 1dfaa0d
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in smontlouis/bible-strong, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Wizard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wizard this skillsmontlouis/bible-strong | 171 | 1 repos | ~1k | Automated safety check: Notes | GPL-3.0 | |
| Nuget Trusted Publishingdotnet/skills | 5.6k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Michel Monitor Pull Request GitHub ActionsPackmindHub/packmind | 317 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Bats Shell Testing Patternswshobson/agents | 40k | 12 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Templatesbartstc/vite-ts-react-template | 122 | 14 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Michel Monitor Pull Request GitHub Actions
PackmindHub/packmind
Diagnose a failed, stuck, or never-triggered CI run on a GitHub PR, apply a local fix if possible, push it, and document the result in a single running PR comment.
Bats Shell Testing Patterns
wshobson/agents
Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
GitHub Actions Templates
bartstc/vite-ts-react-template
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.
Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
More from smontlouis/bible-strong
All 12 skills in this repoNeon Postgres
smontlouis/bible-strong
Guides and best practices for working with Lakebase Postgres, the database behind Neon.
Bible Strong Illustrations
smontlouis/bible-strong
Create or adapt Bible Strong illustrations in the house style of flat colors, monochromatic characters, and fine detail lines.
Setup TS Deep Modules
smontlouis/bible-strong
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files.
Bible To Strong
smontlouis/bible-strong
Deterministic Strong-Bible command workflow for this repository.
Review And Merge PRs
smontlouis/bible-strong
Sequentially review and merge GitHub pull requests one at a time.
Neon
smontlouis/bible-strong
Overview of Neon, a complete set of cloud backend primitives for apps and agents, spanning Lakebase Postgres, Auth, the Data API, Object Storage, Compute Functions, and the AI Gateway.
Related
Works with
Categories
Questions about Wizard
What does Wizard do?
Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each…. Wizard is an agent skill from smontlouis/bible-strong.env files and GitHub Actions secrets.
When should I use Wizard?
Wizard fits situations like: tasks that involve CI/CD.
How do I install Wizard in Claude Code?
Run `npx skills add smontlouis/bible-strong --skill wizard -a claude-code`. Or copy the skill folder (.agents/skills/wizard in smontlouis/bible-strong) into .claude/skills/wizard in your project. Claude Code loads it when a task matches its description.
How do I install Wizard in Codex?
Run `npx skills add smontlouis/bible-strong --skill wizard -a codex`. Or copy the skill folder (.agents/skills/wizard in smontlouis/bible-strong) into .agents/skills/wizard in your project. Codex loads it when a task matches its description.
Can I use Wizard in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add smontlouis/bible-strong --skill wizard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wizard, .gemini/skills/wizard, .github/skills/wizard and .opencode/skills/wizard in your project.
What does Wizard need to run?
Going by SKILL.md and its folder, Wizard needs a shell for the scripts in its folder and the command-line tools its instructions call (gh and bash). Our summary lists: A Bash shell; Docker.
Does Wizard access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Wizard safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Wizard use?
Wizard is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wizard use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wizard?
Skills that share tags, products or a category with Wizard: Nuget Trusted Publishing (dotnet/skills, 5.6k stars), Michel Monitor Pull Request GitHub Actions (PackmindHub/packmind, 317 stars), Bats Shell Testing Patterns (wshobson/agents, 40k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wizard?
smontlouis (a GitHub user) maintains it in smontlouis/bible-strong, which has 171 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: smontlouis/bible-strong on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.