Sets one monorepo's rules for toolchain pins, pnpm package operations, the shared dependency catalog and moon tasks, so the agent adds versions and scripts the right way.
$ npx skills add pierrecomputer/pierre --skill tooling-and-dependencies -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pierrecomputer/pierre tooling-and-dependencies --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/pierrecomputer/pierre.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tooling-and-dependencies .claude/skills/tooling-and-dependencies && 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 "tooling-and-dependencies" agent skill from https://github.com/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependencies into .claude/skills/tooling-and-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-and-dependencies", 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/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependenciesType 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 pierrecomputer/pierre --skill tooling-and-dependencies -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pierrecomputer/pierre tooling-and-dependencies --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pierrecomputer/pierre.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/tooling-and-dependencies .agents/skills/tooling-and-dependencies && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tooling-and-dependencies" agent skill from https://github.com/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependencies into .agents/skills/tooling-and-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-and-dependencies", 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 pierrecomputer/pierre --skill tooling-and-dependencies -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pierrecomputer/pierre tooling-and-dependencies --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pierrecomputer/pierre.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/tooling-and-dependencies .cursor/skills/tooling-and-dependencies && 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 "tooling-and-dependencies" agent skill from https://github.com/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependencies into .cursor/skills/tooling-and-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-and-dependencies", 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/pierrecomputer/pierre.git --path .agents/skills/tooling-and-dependencies--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 pierrecomputer/pierre --skill tooling-and-dependencies -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pierrecomputer/pierre tooling-and-dependencies --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pierrecomputer/pierre.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/tooling-and-dependencies .gemini/skills/tooling-and-dependencies && 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 "tooling-and-dependencies" agent skill from https://github.com/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependencies into .gemini/skills/tooling-and-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-and-dependencies", 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 pierrecomputer/pierre tooling-and-dependenciesInstalls 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 pierrecomputer/pierre --skill tooling-and-dependencies -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pierrecomputer/pierre.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/tooling-and-dependencies .github/skills/tooling-and-dependencies && 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 "tooling-and-dependencies" agent skill from https://github.com/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependencies into .github/skills/tooling-and-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-and-dependencies", 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 pierrecomputer/pierre --skill tooling-and-dependencies -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pierrecomputer/pierre tooling-and-dependencies --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pierrecomputer/pierre.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/tooling-and-dependencies .opencode/skills/tooling-and-dependencies && 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 "tooling-and-dependencies" agent skill from https://github.com/pierrecomputer/pierre/tree/main/.agents/skills/tooling-and-dependencies into .opencode/skills/tooling-and-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-and-dependencies", 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.
tooling-and-dependenciesSets one monorepo's rules for toolchain pins, pnpm package operations, the shared dependency catalog and moon tasks, so the agent adds versions and scripts the right way.
This skill records a monorepo's tooling conventions. Tool versions for bun, pnpm, node, moon and gh are pinned in `.prototools` and managed by proto, so a version is bumped by editing that file only, and moon's version is also kept in step in `.moon/workspace.yml` and a catalog entry. `pnpm` handles package operations such as install, add, remove, lockfile and publish work, while Bun stays as the direct TypeScript runtime and test runner where moon tasks use it.
Dependencies come from the `catalog` in `pnpm-workspace.yaml`: the agent adds an exact version there and references it from a package as `catalog:`, and never runs `pnpm add` inside a package directory. Published packages may intentionally keep version ranges. Build, dev, test and lint entrypoints are moon tasks defined in `.moon/tasks/*.yml` and each project's `moon.yml`, run with `moon run` or `moonx`, and `package.json` scripts exist only for npm lifecycle hooks. The excerpt is cut off, so later sections are not covered.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d302ea0. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
pnpmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
moonrepo.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Monorepo Tooling and Dependencies loads about 1.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 527 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.
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.
The full file from pierrecomputer/pierre at commit d302ea0, republished under its Apache-2.0 licence (© pierrecomputer). 527 words, ~1,122 tokens.
.claude/skills/tooling-and-dependencies/SKILL.md (or your agent's skills folder)..prototools and
managed by proto; its shims put the pinned
versions on PATH inside the repo. proto use installs everything after a pin
changes..prototools only — never install tools globally or
pin versions elsewhere. moon's version is additionally enforced by
versionConstraint in .moon/workspace.yml and mirrored as the
@moonrepo/cli catalog entry (for Vercel builders without proto); keep all
three in sync.moonrepo/setup-toolchain, which runs proto install against the same
.prototools.pnpm for package operations: install, add, remove, dedupe, lockfile,
package-runner, and publish work.bun, npm, yarn, npx, or other package runners for package
operations unless there is a specific documented reason..ts files without a separate
compile step.This monorepo uses the catalog in pnpm-workspace.yaml.
package.json by
default.pnpm-workspace.yaml under catalog, for example
"new-package": "1.2.3"."new-package": "catalog:".pnpm add <package> inside a package directory; it writes direct
versions and breaks the catalog pattern unless you manually normalize them.apps/docs should use catalog versions; published packages such as
packages/diffs may use ranges only when that is intentional.prepublishOnly). Never add task scripts back
to a package.json..moon/tasks/*.yml (inherited) and each project's
moon.yml. Repo-wide tooling (format, lint, icons, clean) lives on the root
project.moon run <project>:<task>
moonx <project>:<task> # same engine; shorthand for moon exec
moonx <project>:<task> -- --flags # forward arguments after --
moon run :test # a task across every project that has it
moon tasks <project> # discover a project's tasksmoon run and moonx (an alias binary for moon exec) execute the same action
pipeline: identical dependency resolution, caching, and affected support. Use
them interchangeably; docs write moon run for canonical commands and moonx
in interactive examples. The one practical difference: moonx/moon exec
exposes CI-behavior overrides (--ignore-ci-checks, --ci <bool>) that
moon run lacks. moon ci is a third thing — the affected-aware orchestrator
used only by .github/workflows/ci.yml; never reach for it locally.
moon builds dependency projects first (deps: ['^:build']), caches outputs, and
skips tasks whose inputs have not changed. Local-only tasks set explicit options
instead of moon presets (presets force runInCI: skip, which moon refuses to
run in CI-detected shells; agent harnesses export CI=1):
runInCI: 'always' — runnable everywhere, and never in the
CI pipeline because a task with no deps or dependents is never affected
through the graph.runInCI: 'skip' — moon ci --include-relations runs affected
runInCI-enabled tasks even when unrequested, which would pull them into CI.
Run them in CI-marked shells with moonx <target> --ignore-ci-checks (works
regardless of the shell's CI env). For non-moon commands that CI-gate
themselves, unset the var instead: CI= pnpm publish --dry-run.© pierrecomputer, 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
Just SKILL.md in .agents/skills/tooling-and-dependencies of pierrecomputer/pierre.
Open the folder on GitHubat commit d302ea0
Monorepo Tooling and Dependencies 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 |
|---|---|---|---|---|---|---|
| Monorepo Tooling and Dependencies this skillpierrecomputer/pierre | 6.2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Linea Dependency MaintenanceConsensys-Incorporated/linea-attestation-registry | 177 | 1 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Link Workspace Packagesnomcopter/react-mosaic | 4.8k | 5 repos | ~760 | Automated safety check: Pass | Custom licence | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| TS SDK Authormindfold-ai/Trellis | 15k | — | ~6.1k | Automated safety check: Pass | MIT | |
| Fix Security PRunional/typescript-blackbook | 133 | — | ~1.4k | Automated safety check: Warn | MIT |
Consensys-Incorporated/linea-attestation-registry
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…
nomcopter/react-mosaic
Link workspace packages in monorepos (npm, yarn, pnpm, bun).
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
mindfold-ai/Trellis
Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo.
unional/typescript-blackbook
Fix a PR that is failing due to security or vulnerability issues — npm/pnpm/yarn/bun audit failures, CVE alerts, Dependabot merge conflicts, Snyk failures, or GitHub security advisory blocks.
mweinbach/agent-coworker
Quick reference for using Bun to run TypeScript and JavaScript, install packages, bundle code, run tests and serve HTTP, with the key files and commands.
pierrecomputer/pierre
Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.
pierrecomputer/pierre
Explains how to use the @pierre/theming package to list, resolve, select, switch and persist themes, with controller, color and React references.
pierrecomputer/pierre
Use when an app uses @pierre/trees to render or control a file tree, including React, vanilla JavaScript, SSR, web components, selection, search, rename, drag…
pierrecomputer/pierre
Shows how to use @pierre/highlights for syntax-highlighted HTML or tokens, streaming and incremental tokenizing, and Zed-compatible themes with CSS variables.
pierrecomputer/pierre
Chooses the right verification step after a code change in Pierre's monorepo: format and lint, a typecheck, Bun unit tests, snapshots, or Playwright E2E.
pierrecomputer/pierre
Shows an agent how to install and use the @pierre/theme package, which ships ten Pierre light and dark color themes for Shiki and VS Code.
Works with
Categories
Sets one monorepo's rules for toolchain pins, pnpm package operations, the shared dependency catalog and moon tasks, so the agent adds versions and scripts the right way. This skill records a monorepo's tooling conventions.yml` and a catalog entry.
Monorepo Tooling and Dependencies fits situations like: adding or upgrading a dependency in the monorepo; editing a package.json or publishing a package; deciding whether a command should use pnpm or Bun; running build, test or lint tasks through moon.
Run `npx skills add pierrecomputer/pierre --skill tooling-and-dependencies -a claude-code`. Or copy the skill folder (.agents/skills/tooling-and-dependencies in pierrecomputer/pierre) into .claude/skills/tooling-and-dependencies in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pierrecomputer/pierre --skill tooling-and-dependencies -a codex`. Or copy the skill folder (.agents/skills/tooling-and-dependencies in pierrecomputer/pierre) into .agents/skills/tooling-and-dependencies in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pierrecomputer/pierre --skill tooling-and-dependencies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tooling-and-dependencies, .gemini/skills/tooling-and-dependencies, .github/skills/tooling-and-dependencies and .opencode/skills/tooling-and-dependencies in your project.
Going by SKILL.md and its folder, Monorepo Tooling and Dependencies needs the command-line tools its instructions call (pnpm). Our summary lists: proto, pnpm, Bun and moon at the versions pinned in `.prototools`.
SKILL.md names 1 domain. As links in the text: moonrepo.dev. This is read from the text; nothing was executed.
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.
Monorepo Tooling and Dependencies 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.
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Monorepo Tooling and Dependencies: Linea Dependency Maintenance (Consensys-Incorporated/linea-attestation-registry, 177 stars), Link Workspace Packages (nomcopter/react-mosaic, 4.8k stars), Pnpm Engine (teambit/bit, 18k stars) and TS SDK Author (mindfold-ai/Trellis, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
pierrecomputer (a GitHub organization) maintains it in pierrecomputer/pierre, which has 6,243 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.
Source: pierrecomputer/pierre on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
