Nx Run Tasks
nomcopter/react-mosaic
Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.
Bootstraps this repo's toolchain (task, actionlint, shellcheck, shfmt, bats, uv, node, openspec, renovate) into repo-local .tools/bin, .tools/bats/bin and .tools/node/bin directories and puts them…
Install Setup Repo Tooling
$ npx skills add agntcy/coffeeAgntcy --skill setup-repo-tooling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agntcy/coffeeAgntcy setup-repo-tooling --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/agntcy/coffeeAgntcy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repo-tooling/setup-repo-tooling .claude/skills/setup-repo-tooling && 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 "setup-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-tooling into .claude/skills/setup-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-repo-tooling", 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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-toolingType 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 agntcy/coffeeAgntcy --skill setup-repo-tooling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agntcy/coffeeAgntcy setup-repo-tooling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/repo-tooling/setup-repo-tooling .agents/skills/setup-repo-tooling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setup-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-tooling into .agents/skills/setup-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-repo-tooling", 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 agntcy/coffeeAgntcy --skill setup-repo-tooling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agntcy/coffeeAgntcy setup-repo-tooling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/repo-tooling/setup-repo-tooling .cursor/skills/setup-repo-tooling && 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 "setup-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-tooling into .cursor/skills/setup-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-repo-tooling", 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/agntcy/coffeeAgntcy.git --path .agents/skills/repo-tooling/setup-repo-tooling--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 agntcy/coffeeAgntcy --skill setup-repo-tooling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agntcy/coffeeAgntcy setup-repo-tooling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/repo-tooling/setup-repo-tooling .gemini/skills/setup-repo-tooling && 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 "setup-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-tooling into .gemini/skills/setup-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-repo-tooling", 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 agntcy/coffeeAgntcy setup-repo-toolingInstalls 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 agntcy/coffeeAgntcy --skill setup-repo-tooling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/repo-tooling/setup-repo-tooling .github/skills/setup-repo-tooling && 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 "setup-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-tooling into .github/skills/setup-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-repo-tooling", 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 agntcy/coffeeAgntcy --skill setup-repo-tooling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agntcy/coffeeAgntcy setup-repo-tooling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/repo-tooling/setup-repo-tooling .opencode/skills/setup-repo-tooling && 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 "setup-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/setup-repo-tooling into .opencode/skills/setup-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-repo-tooling", 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
setup-repo-tooling- GitHub stars
- 112
- Token cost
- ~883 tokens
- SKILL.md length
- 374 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Bootstraps this repo's toolchain (task, actionlint, shellcheck, shfmt, bats, uv, node, openspec, renovate) into repo-local .tools/bin, .tools/bats/bin and .tools/node/bin directories and puts them…
- Development work in your project
- SKILL.md covers When to use, What it does, Steps and Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Setup Repo Tooling is an agent skill from agntcy/coffeeAgntcy. Bootstraps this repo's toolchain (task, actionlint, shellcheck, shfmt, bats, uv, node, openspec, renovate) into repo-local .tools/bin, .tools/bats/bin and .tools/node/bin directories and puts them on PATH for the session. Use before running any other task in this repo, or whenever task, actionlint, shellcheck, shfmt, bats, uv, node, npm, openspec, or renovate are reported as not found.
Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with npm. The repository describes itself as: End-to-end reference application for AGNTCY Components. The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “Use the setup-repo-tooling skill to bootstrap this repo's toolchain (task, actionlint, shellcheck, shfmt, bats, uv, node, openspec, renovate) into…”
- “/setup-repo-tooling”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 78f588c. 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
Setup Repo Tooling loads about 883 tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 374 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
The full file from agntcy/coffeeAgntcy at commit 78f588c, republished under its Apache-2.0 licence (© agntcy). 374 words, ~883 tokens.
Download SKILL.mdSave it as
.claude/skills/setup-repo-tooling/SKILL.md (or your agent's skills folder).- name
- setup-repo-tooling
- description
- Bootstraps this repo's toolchain (task, actionlint, shellcheck, shfmt, bats, uv, node, openspec, renovate) into repo-local .tools/bin, .tools/bats/bin and .tools/node/bin directories and puts them on PATH for the session. Use before running any other task in this repo, or whenever `task`, `actionlint`, `shellcheck`, `shfmt`, `bats`, `uv`, `node`, `npm`, `openspec`, or `renovate` are reported as not found.
Set up repo tooling
When to use
Before doing anything else in this repo, or when a command fails with
task: command not found / actionlint: command not found / shellcheck: command not found / shfmt: command not found / bats: command not found / uv: command not found / node: command not found / npm: command not found / openspec: command not found / renovate: command not found.
This skill is the one deliberate exception to the script -> Taskfile task
-> skill hierarchy described in
.agents/rules/meta/repo-operation-pipeline.md:
it calls scripts/setup.sh directly rather than through a task command,
because task itself doesn't exist yet on a fresh clone - bootstrapping it
through the Taskfile would be circular.
What it does
scripts/setup.sh installs task, actionlint, shellcheck, shfmt,
bats, uv, node, openspec, and renovate into .tools/ - inside this repo only, never the
user's global PATH, shell profile, or home directory - and is safe to
re-run any time (it's a no-op if everything is already present at its
pinned version, per
.agents/rules/meta/pinned-tool-versions.md).
If neither curl nor wget is present, it installs curl itself via
whatever OS package manager is already on the machine (or prints manual
instructions if it can't).
openspec (@fission-ai/openspec) and renovate ship as npm packages
rather than standalone binaries, so setup.sh bootstraps its own pinned
Node.js first and installs both with that Node's npm. Node lands in
.tools/node/ rather than the flat .tools/bin/, because its npm/npx
are symlinks resolved relative to a sibling lib/node_modules/npm/ and
can't be moved independently of that directory the way every other tool's
single relocatable binary can - scripts/env.sh puts both .tools/bin
and .tools/node/bin on PATH to cover it. bats likewise ships as a
bin/ + libexec/ + lib/ tree, so it lands in .tools/bats/, whose
bin/ scripts/env.sh also puts on PATH.
Show full SKILL.md (93 more words)Show less
Steps
- [ ] 1. Run: ./scripts/setup.sh
- [ ] 2. Run: source scripts/env.sh (puts .tools/bin, .tools/node/bin and .tools/bats/bin on PATH for this shell)
- [ ] 3. Confirm: task --list (should print every task with no errors)If task is already on PATH some other way (e.g. installed via a
package manager), task setup does the same thing as step 1 - either
entry point runs the identical idempotent script.
Rules
- Never hand-install
task/actionlint/shellcheck/shfmt/bats/uv/nodesome other way (Homebrew, apt, nvm, a differently pinned curl command) - always go throughscripts/setup.shso the version pinned inscripts/lib/versions.shis what actually gets used. - If a pinned version needs bumping, or a tool needs to be added to or
removed from the toolchain, see the
manage-repo-toolingskill - do not hardcode a version anywhere else.
© agntcy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/repo-tooling/setup-repo-tooling of agntcy/coffeeAgntcy.
Open the folder on GitHubat commit 78f588c
Compare with similar skills
Setup Repo Tooling 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 |
|---|---|---|---|---|---|---|
| Setup Repo Tooling this skillagntcy/coffeeAgntcy | 112 | — | ~883 | Automated safety check: Pass | Apache-2.0 | |
| Nx Run Tasksnomcopter/react-mosaic | 4.8k | 8 repos | ~613 | Automated safety check: Pass | Custom licence | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Open Code Review CLIalibaba/open-code-review | 46k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Open Code Review Delegate
alibaba/open-code-review
Has the host agent do the code review itself while the ocr CLI handles file selection and rule lookup, covering workspace changes, branch ranges or single commits.
More from agntcy/coffeeAgntcy
All 20 skills in this repoA2a Protocol
agntcy/coffeeAgntcy
A skill your agent uses when the user asks about A2A (Agent-to-Agent) protocol communication, OASF record formats, AGNTCY directory operations, agent card parsing, or dirctl CLI usage.
Add Repo Operation
agntcy/coffeeAgntcy
Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline.
Agentic Workflows API Documentation Lungo
agntcy/coffeeAgntcy
Authors and maintains the human-facing Agentic Workflows API documentation for the lungo subproject at coffeeAGNTCY/coffeeagents/lungo/docs/workflow-instanceapi.md.
Checking Helm Chart Version Bumps
agntcy/coffeeAgntcy
Checks whether any Helm chart under coffeeAGNTCY/coffeeagents/{corto,lungo}/deployment/helm// has content changes not covered by a later Chart.yaml version: bump, anywhere in that chart's history…
Checking Pinned References
agntcy/coffeeAgntcy
Runs task pins:check to find any third-party GitHub Action, reusable-workflow, or image reference that isn't pinned to an immutable SHA/digest, and pins each one it finds.
Checking Workflow Permissions
agntcy/coffeeAgntcy
Runs task workflows:check-permissions to find any GitHub Actions workflow file with a write-all grant or no declared permissions, and scopes it down to least privilege.
Related
Works with
Categories
Questions about Setup Repo Tooling
What does Setup Repo Tooling do?
Bootstraps this repo's toolchain (task, actionlint, shellcheck, shfmt, bats, uv, node, openspec, renovate) into repo-local .tools/bin, .tools/bats/bin and .tools/node/bin directories and puts them…. Setup Repo Tooling is an agent skill from agntcy/coffeeAgntcy.tools/node/bin directories and puts them on PATH for the session.
When should I use Setup Repo Tooling?
Setup Repo Tooling fits situations like: development work in your project.
How do I install Setup Repo Tooling in Claude Code?
Run `npx skills add agntcy/coffeeAgntcy --skill setup-repo-tooling -a claude-code`. Or copy the skill folder (.agents/skills/repo-tooling/setup-repo-tooling in agntcy/coffeeAgntcy) into .claude/skills/setup-repo-tooling in your project. Claude Code loads it when a task matches its description.
How do I install Setup Repo Tooling in Codex?
Run `npx skills add agntcy/coffeeAgntcy --skill setup-repo-tooling -a codex`. Or copy the skill folder (.agents/skills/repo-tooling/setup-repo-tooling in agntcy/coffeeAgntcy) into .agents/skills/setup-repo-tooling in your project. Codex loads it when a task matches its description.
Can I use Setup Repo Tooling 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 agntcy/coffeeAgntcy --skill setup-repo-tooling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup-repo-tooling, .gemini/skills/setup-repo-tooling, .github/skills/setup-repo-tooling and .opencode/skills/setup-repo-tooling in your project.
What does Setup Repo Tooling need to run?
SKILL.md names no scripts, command-line tools or credentials: Setup Repo Tooling is instructions for the agent only. Our summary lists: Node.js.
Does Setup Repo Tooling 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 Setup Repo Tooling 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 Setup Repo Tooling use?
Setup Repo Tooling is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Setup Repo Tooling use?
About 883 tokens (SKILL.md is roughly 3.5k 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 Setup Repo Tooling?
Skills that share tags, products or a category with Setup Repo Tooling: Nx Run Tasks (nomcopter/react-mosaic, 4.8k stars), Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars) and Cutting A Release (TriliumNext/Trilium, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Setup Repo Tooling?
agntcy (a GitHub organization) maintains it in agntcy/coffeeAgntcy, which has 112 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 9, 2026.
Source: agntcy/coffeeAgntcy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.