Ecc Recipes
affaan-m/ECC
Map a described workflow to the right ECC command group with run-order and stop condition, or browse all command-group recipe families read live from the commands directory.
Recipe for adding or extending a CLI tool wrapper under src/Fallout.Common/Tools/<Tool/<Tool.json.
Custom licenceAuto-check passed
Install Adding A Tool Wrapper
$ npx skills add Fallout-build/Fallout --skill adding-a-tool-wrapper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Fallout-build/Fallout adding-a-tool-wrapper --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/Fallout-build/Fallout.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-a-tool-wrapper .claude/skills/adding-a-tool-wrapper && 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 "adding-a-tool-wrapper" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapper into .claude/skills/adding-a-tool-wrapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-tool-wrapper", 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/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapperType 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 Fallout-build/Fallout --skill adding-a-tool-wrapper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Fallout-build/Fallout adding-a-tool-wrapper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/adding-a-tool-wrapper .agents/skills/adding-a-tool-wrapper && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adding-a-tool-wrapper" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapper into .agents/skills/adding-a-tool-wrapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-tool-wrapper", 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 Fallout-build/Fallout --skill adding-a-tool-wrapper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Fallout-build/Fallout adding-a-tool-wrapper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/adding-a-tool-wrapper .cursor/skills/adding-a-tool-wrapper && 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 "adding-a-tool-wrapper" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapper into .cursor/skills/adding-a-tool-wrapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-tool-wrapper", 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/Fallout-build/Fallout.git --path .agents/skills/adding-a-tool-wrapper--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 Fallout-build/Fallout --skill adding-a-tool-wrapper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Fallout-build/Fallout adding-a-tool-wrapper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/adding-a-tool-wrapper .gemini/skills/adding-a-tool-wrapper && 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 "adding-a-tool-wrapper" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapper into .gemini/skills/adding-a-tool-wrapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-tool-wrapper", 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 Fallout-build/Fallout adding-a-tool-wrapperInstalls 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 Fallout-build/Fallout --skill adding-a-tool-wrapper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/adding-a-tool-wrapper .github/skills/adding-a-tool-wrapper && 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 "adding-a-tool-wrapper" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapper into .github/skills/adding-a-tool-wrapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-tool-wrapper", 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 Fallout-build/Fallout --skill adding-a-tool-wrapper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Fallout-build/Fallout adding-a-tool-wrapper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Fallout-build/Fallout.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/adding-a-tool-wrapper .opencode/skills/adding-a-tool-wrapper && 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 "adding-a-tool-wrapper" agent skill from https://github.com/Fallout-build/Fallout/tree/develop/.agents/skills/adding-a-tool-wrapper into .opencode/skills/adding-a-tool-wrapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-tool-wrapper", 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
adding-a-tool-wrapper- GitHub stars
- 165
- Token cost
- ~279 tokens
- SKILL.md length
- 122 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Recipe for adding or extending a CLI tool wrapper under src/Fallout.Common/Tools/<Tool/<Tool.json.
- Works in 7 steps: Find the closest existing tool under… → Cover a full command with all its… → Use formatting tags in help text → …
- Asked to add a new tool wrapper
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Add a command/argument to an existing one
What it does
Adding A Tool Wrapper is an agent skill from Fallout-build/Fallout. Recipe for adding or extending a CLI tool wrapper under src/Fallout.Common/Tools/<Tool/<Tool.json. Trigger when asked to add a new tool wrapper, add a command/argument to an existing one, or when a Tools/.json file is being edited.
Its SKILL.md is about 280 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: ☢️ Fallout — The C/.NET Build System.
When your agent uses it
- Asked to add a new tool wrapper
- Add a command/argument to an existing one
- A Tools/.json file is being edited
Example prompts
- “/adding-a-tool-wrapper”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Find the closest existing tool under src/Fallout.Common/Tools//.json
- Cover a full command with all its arguments, not just the one option you need.
- Use formatting tags in help text
- Don't write secret: false — it's the default.
- Don't write default: xxx — obsolete field, omit it.
- Run ./build.ps1 GenerateTools to regenerate the .cs output.
- Commit the regenerated .cs alongside the .json spec in the same commit —
What it can do on your machine
Read from SKILL.md and the folder at commit 8333cc8. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Adding A Tool Wrapper loads about 279 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 122 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 passed
The automated check found no risky patterns in SKILL.md.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 122 words (~279 tokens).
“Tool wrapper .json files are the source of truth; the .cs next to each one is generated — never hand-edit the generated file.”
- name
- adding-a-tool-wrapper
Files
Just SKILL.md in .agents/skills/adding-a-tool-wrapper of Fallout-build/Fallout.
Open the folder on GitHubat commit 8333cc8
Compare with similar skills
Adding A Tool Wrapper 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 |
|---|---|---|---|---|---|---|
| Adding A Tool Wrapper this skillFallout-build/Fallout | 165 | — | ~279 | Automated safety check: Pass | Custom licence | |
| Ecc Recipesaffaan-m/ECC | 275k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| ScottPlot Cookbook RecipeScottPlot/ScottPlot | 6.8k | — | ~384 | Automated safety check: Pass | MIT | |
| Scaffold Python ADK Recipegoogle/adk-recipes | 10k | — | ~931 | Automated safety check: Pass | Apache-2.0 | |
| Extending Hobby Smoke TestsPostHog/posthog | 40k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Vue Wrapper Devhandsontable/handsontable | 22k | — | ~406 | Automated safety check: Pass | Custom licence |
Similar skills
ScottPlot Cookbook Recipe
ScottPlot/ScottPlot
Adds or extends a ScottPlot Cookbook recipe for a given plottable, in the right PlotTypes category and in the style of neighboring recipes.
- Official
Scaffold Python ADK Recipe
google/adk-recipes
Creates a new Python recipe for the ADK recipes repository by running a scaffold script that copies template files, after confirming the output directory and recipe name.
- Official
Extending Hobby Smoke Tests
PostHog/posthog
Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml.
Vue Wrapper Dev
handsontable/handsontable
A skill your agent uses when developing or modifying the @handsontable/vue3 wrapper package - Vue 3 SFC components, deep watchers, and provide/inject patterns for settings propagation
Seedance Recipes
Emily2040/seedance-2.0
This skill should be used when the user asks for a Seedance 2.0 template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene, or…
More from Fallout-build/Fallout
All 8 skills in this repoCreating A PR
Fallout-build/Fallout
Steps for opening a pull request in the Fallout repo — picking the right base branch, creating it as a draft, applying the target/vCurrent-or-vNext and changelog-category labels, and handling…
Plain English
Fallout-build/Fallout
Write clear, plain English for developer-facing prose aimed at an international audience.
Marking Experimental APIs
Fallout-build/Fallout
How to mark a public API as not-yet-stable with [Experimental("FALLOUT0xx")], or deprecate one with [Obsolete(..., DiagnosticId = "FALLOUTOBS0xx")], including diagnostic-ID allocation.
Editing CI Workflows
Fallout-build/Fallout
Invariants to preserve when touching .github/workflows/, build/Build.CI.GitHubActions.cs, or anything about which branches/tags trigger CI or publish packages.
Restructure PR Commits
Fallout-build/Fallout
Restructure the commits on an existing PR into focused, reviewable commits
Adding A Migration Step
Fallout-build/Fallout
How to make fallout-migrate handle a new rename, removal, or rewrite by extending an existing IMigrationStep, and when a genuinely new step is warranted.
Questions about Adding A Tool Wrapper
What does Adding A Tool Wrapper do?
Recipe for adding or extending a CLI tool wrapper under src/Fallout.Common/Tools/<Tool/<Tool.json. Adding A Tool Wrapper is an agent skill from Fallout-build/Fallout.json.
When should I use Adding A Tool Wrapper?
Adding A Tool Wrapper fits situations like: asked to add a new tool wrapper; add a command/argument to an existing one; A Tools/.json file is being edited.
How do I install Adding A Tool Wrapper in Claude Code?
Run `npx skills add Fallout-build/Fallout --skill adding-a-tool-wrapper -a claude-code`. Or copy the skill folder (.agents/skills/adding-a-tool-wrapper in Fallout-build/Fallout) into .claude/skills/adding-a-tool-wrapper in your project. Claude Code loads it when a task matches its description.
How do I install Adding A Tool Wrapper in Codex?
Run `npx skills add Fallout-build/Fallout --skill adding-a-tool-wrapper -a codex`. Or copy the skill folder (.agents/skills/adding-a-tool-wrapper in Fallout-build/Fallout) into .agents/skills/adding-a-tool-wrapper in your project. Codex loads it when a task matches its description.
Can I use Adding A Tool Wrapper 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 Fallout-build/Fallout --skill adding-a-tool-wrapper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-a-tool-wrapper, .gemini/skills/adding-a-tool-wrapper, .github/skills/adding-a-tool-wrapper and .opencode/skills/adding-a-tool-wrapper in your project.
What does Adding A Tool Wrapper need to run?
SKILL.md names no scripts, command-line tools or credentials: Adding A Tool Wrapper is instructions for the agent only.
Does Adding A Tool Wrapper access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Adding A Tool Wrapper safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Adding A Tool Wrapper use?
Adding A Tool Wrapper has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Adding A Tool Wrapper use?
About 279 tokens (SKILL.md is roughly 1.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 Adding A Tool Wrapper?
Skills that share tags, products or a category with Adding A Tool Wrapper: Ecc Recipes (affaan-m/ECC, 275k stars), ScottPlot Cookbook Recipe (ScottPlot/ScottPlot, 6.8k stars), Scaffold Python ADK Recipe (google/adk-recipes, 10k stars) and Extending Hobby Smoke Tests (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Adding A Tool Wrapper?
Fallout-build (a GitHub organization) maintains it in Fallout-build/Fallout, which has 165 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 3, 2026.
Source: Fallout-build/Fallout on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.