Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Update a pinned tool's version, introduce a new tool, or remove one from this repo's local toolchain (scripts/lib/versions.sh + scripts/setup.sh).
Install Manage Repo Tooling
$ npx skills add agntcy/coffeeAgntcy --skill manage-repo-tooling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agntcy/coffeeAgntcy manage-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/manage-repo-tooling .claude/skills/manage-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 "manage-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/manage-repo-tooling into .claude/skills/manage-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-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/manage-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 manage-repo-tooling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agntcy/coffeeAgntcy manage-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/manage-repo-tooling .agents/skills/manage-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 "manage-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/manage-repo-tooling into .agents/skills/manage-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-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 manage-repo-tooling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agntcy/coffeeAgntcy manage-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/manage-repo-tooling .cursor/skills/manage-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 "manage-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/manage-repo-tooling into .cursor/skills/manage-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-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/manage-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 manage-repo-tooling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agntcy/coffeeAgntcy manage-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/manage-repo-tooling .gemini/skills/manage-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 "manage-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/manage-repo-tooling into .gemini/skills/manage-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-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 manage-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 manage-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/manage-repo-tooling .github/skills/manage-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 "manage-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/manage-repo-tooling into .github/skills/manage-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-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 manage-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 manage-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/manage-repo-tooling .opencode/skills/manage-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 "manage-repo-tooling" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/manage-repo-tooling into .opencode/skills/manage-repo-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-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
manage-repo-tooling- GitHub stars
- 112
- Token cost
- ~887 tokens
- SKILL.md length
- 121 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Update a pinned tool's version, introduce a new tool, or remove one from this repo's local toolchain (scripts/lib/versions.sh + scripts/setup.sh).
- Asked to bump a tool version
- SKILL.md covers When to use, Updating a pinned version, Introducing a new tool and Removing a tool, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Add a new CLI dependency
What it does
Manage Repo Tooling is an agent skill from agntcy/coffeeAgntcy. Update a pinned tool's version, introduce a new tool, or remove one from this repo's local toolchain (scripts/lib/versions.sh + scripts/setup.sh). Use when asked to bump a tool version, add a new CLI dependency, or drop one that's no longer used.
Its SKILL.md is about 890 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. The repository describes itself as: End-to-end reference application for AGNTCY Components. The licence is Apache-2.0.
When your agent uses it
- Asked to bump a tool version
- Add a new CLI dependency
- Drop one thats no longer used
Example prompts
- “s version, introduce a new tool, or remove one from this repo”
- “/manage-repo-tooling”
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
Manage Repo Tooling loads about 887 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 121 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). 121 words, ~887 tokens.
Download SKILL.mdSave it as
.claude/skills/manage-repo-tooling/SKILL.md (or your agent's skills folder).- name
- manage-repo-tooling
- description
- Update a pinned tool's version, introduce a new tool, or remove one from this repo's local toolchain (scripts/lib/versions.sh + scripts/setup.sh). Use when asked to bump a tool version, add a new CLI dependency, or drop one that's no longer used.
Manage repo tooling
When to use
When asked to bump a pinned version in
scripts/lib/versions.sh, add a new
tool to this repo's local .tools/bin toolchain, or remove one that's no
longer needed. This is a repo-maintainer activity on the toolchain's
pins - different from the setup-repo-tooling skill, which just runs
what's already pinned.
Updating a pinned version
- [ ] 1. Edit the <TOOL>_VERSION in scripts/lib/versions.sh - the single source of truth.
- [ ] 2. Run: task setup (or ./scripts/setup.sh). It compares the installed version against the pin and reinstalls on any mismatch, so this actually picks up the bump - it isn't a no-op just because a binary already exists.
- [ ] 3. Confirm: <tool> --version (or -version) matches the new pin.
- [ ] 4. Run: task check:all - a version bump can change lint/format output (shellcheck/shfmt/actionlint findings can shift between versions).Introducing a new tool
- [ ] 1. Add <TOOL>_VERSION, with its `# renovate:` annotation line above it, to scripts/lib/versions.sh in alphabetical position (the install blocks in scripts/setup.sh stay in dependency order instead).
- [ ] 2. Add an install block to scripts/setup.sh, matching the shape of however the tool distributes itself: an official install script piped to sh (like task), a static binary release fetched via FETCH + scripts/lib/platform.sh's OS/arch detection (like actionlint/shellcheck/shfmt), or an npm package installed via the bootstrapped Node's npm --prefix .tools (like openspec - see how node/openspec are wired for the shape of a tool that needs its own runtime first). Guard it the same way every existing block is guarded - see the pinned-tool-versions rule.
- [ ] 3. Wire whatever new script/task actually needs the tool - see the add-repo-operation skill if this is for a brand-new operation.
- [ ] 4. Update every place the toolchain is named: CONTRIBUTING.md, AGENTS.md, .agents/skills/repo-tooling/setup-repo-tooling/SKILL.md's tool list, Taskfile.yaml's setup task description.
- [ ] 5. Simulate a fresh clone: move .tools/ aside (mv .tools /tmp/tools-bak), run task setup, confirm it installs cleanly, then remove the backup once confirmed.
- [ ] 6. Run: task check:all.Removing a tool
- [ ] 1. Remove its install block from scripts/setup.sh and its _VERSION from scripts/lib/versions.sh.
- [ ] 2. Grep the whole repo for the tool's name and remove or update every mention - CONTRIBUTING.md, AGENTS.md, .agents/skills/repo-tooling/setup-repo-tooling/SKILL.md, Taskfile.yaml descriptions, any rule/skill/script that shells out to it.
- [ ] 3. Confirm nothing still invokes it: grep scripts/ and .github/workflows/ for its binary name.
- [ ] 4. Simulate a fresh clone (see step 5 above) and run task check:all.Rules
scripts/lib/versions.shis the single source of truth for every pinned version - never hardcode one anywhere else (see thesetup-repo-toolingskill).- None of these three operations get a dedicated CI check - see the
pinned-tool-versionsrule for why, and what stands in for one. - Keep every doc that names the toolchain in sync in the same change - see
self-review-after-change.
© 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/manage-repo-tooling of agntcy/coffeeAgntcy.
Open the folder on GitHubat commit 78f588c
Compare with similar skills
Manage 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 |
|---|---|---|---|---|---|---|
| Manage Repo Tooling this skillagntcy/coffeeAgntcy | 112 | — | ~887 | Automated safety check: Pass | Apache-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
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
Categories
Questions about Manage Repo Tooling
What does Manage Repo Tooling do?
Update a pinned tool's version, introduce a new tool, or remove one from this repo's local toolchain (scripts/lib/versions.sh + scripts/setup.sh). Manage Repo Tooling is an agent skill from agntcy/coffeeAgntcy.sh).
When should I use Manage Repo Tooling?
Manage Repo Tooling fits situations like: asked to bump a tool version; add a new CLI dependency; drop one thats no longer used.
How do I install Manage Repo Tooling in Claude Code?
Run `npx skills add agntcy/coffeeAgntcy --skill manage-repo-tooling -a claude-code`. Or copy the skill folder (.agents/skills/repo-tooling/manage-repo-tooling in agntcy/coffeeAgntcy) into .claude/skills/manage-repo-tooling in your project. Claude Code loads it when a task matches its description.
How do I install Manage Repo Tooling in Codex?
Run `npx skills add agntcy/coffeeAgntcy --skill manage-repo-tooling -a codex`. Or copy the skill folder (.agents/skills/repo-tooling/manage-repo-tooling in agntcy/coffeeAgntcy) into .agents/skills/manage-repo-tooling in your project. Codex loads it when a task matches its description.
Can I use Manage 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 manage-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/manage-repo-tooling, .gemini/skills/manage-repo-tooling, .github/skills/manage-repo-tooling and .opencode/skills/manage-repo-tooling in your project.
What does Manage Repo Tooling need to run?
SKILL.md names no scripts, command-line tools or credentials: Manage Repo Tooling is instructions for the agent only.
Does Manage 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 Manage 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 Manage Repo Tooling use?
Manage 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 Manage Repo Tooling use?
About 887 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 Manage Repo Tooling?
Skills that share tags, products or a category with Manage Repo Tooling: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Manage 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.