Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
Hermetic Bazel build, test, and packaging commands for the Moosync project.
Install Bazel
$ npx skills add Moosync/Moosync --skill bazel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Moosync/Moosync bazel --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/Moosync/Moosync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bazel .claude/skills/bazel && 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 "bazel" agent skill from https://github.com/Moosync/Moosync/tree/main/.agents/skills/bazel into .claude/skills/bazel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel", 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/Moosync/Moosync/tree/main/.agents/skills/bazelType 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 Moosync/Moosync --skill bazel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Moosync/Moosync bazel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Moosync/Moosync.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/bazel .agents/skills/bazel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bazel" agent skill from https://github.com/Moosync/Moosync/tree/main/.agents/skills/bazel into .agents/skills/bazel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel", 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 Moosync/Moosync --skill bazel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Moosync/Moosync bazel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Moosync/Moosync.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/bazel .cursor/skills/bazel && 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 "bazel" agent skill from https://github.com/Moosync/Moosync/tree/main/.agents/skills/bazel into .cursor/skills/bazel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel", 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/Moosync/Moosync.git --path .agents/skills/bazel--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 Moosync/Moosync --skill bazel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Moosync/Moosync bazel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Moosync/Moosync.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/bazel .gemini/skills/bazel && 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 "bazel" agent skill from https://github.com/Moosync/Moosync/tree/main/.agents/skills/bazel into .gemini/skills/bazel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel", 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 Moosync/Moosync bazelInstalls 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 Moosync/Moosync --skill bazel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Moosync/Moosync.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/bazel .github/skills/bazel && 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 "bazel" agent skill from https://github.com/Moosync/Moosync/tree/main/.agents/skills/bazel into .github/skills/bazel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel", 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 Moosync/Moosync --skill bazel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Moosync/Moosync bazel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Moosync/Moosync.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/bazel .opencode/skills/bazel && 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 "bazel" agent skill from https://github.com/Moosync/Moosync/tree/main/.agents/skills/bazel into .opencode/skills/bazel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel", 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
bazel- GitHub stars
- 259
- Token cost
- ~722 tokens
- SKILL.md length
- 241 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Hermetic Bazel build, test, and packaging commands for the Moosync project.
- Works in 4 steps: Never run bazel clean unless explicitly… → Use the @pkg repository to trigger… → For incremental builds, rely on Bazel's… → …
- Tasks that involve Dependency management
- SKILL.md covers Description, Commands, Usage Guidelines and Example Workflow, plus 2 more sections
- Calls bazel and git
What it does
Bazel is an agent skill from Moosync/Moosync. Hermetic Bazel build, test, and packaging commands for the Moosync project. Covers building all targets through rulesrust, running tests, creating distribution packages via @pkg//:all, dependency management with bzlmod (MODULE.bazel), sandbox-safe builds, and patching external rules.
Its SKILL.md is about 720 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, covering Dependency management. It works with Rust. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Dependency management
Example prompts
- “/bazel”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Never run bazel clean unless explicitly requested by a user; it can invalidate cached outputs and mask real build issues.
- Use the @pkg repository to trigger packaging for all supported platforms.
- For incremental builds, rely on Bazel's caching rather than manual cleaning.
- Never add extra flags or change the platform while building bazel rules unless explicitly specified by the user.
What it can do on your machine
Read from SKILL.md and the folder at commit a2b81ce. 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
Shell commands in SKILL.md call:
bazelgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Bazel loads about 722 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 241 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 Moosync/Moosync at commit a2b81ce, republished under its GPL-3.0 licence (© Moosync). 241 words, ~722 tokens.
Download SKILL.mdSave it as
.claude/skills/bazel/SKILL.md (or your agent's skills folder).- name
- bazel
- description
- Hermetic Bazel build, test, and packaging commands for the Moosync project. Covers building all targets through rules_rust, running tests, creating distribution packages via @pkg//:all, dependency management with bzlmod (MODULE.bazel), sandbox-safe builds, and patching external rules.
Bazel Skill
Description
The Bazel skill wraps common Bazel commands used throughout the Moosync repository. It enforces hermetic builds and provides quick shortcuts for building targets, running tests, and packaging the entire project.
Hermeticity is a core requirement: all dependencies must be declared in
BUILD.bazelfiles or fetched viarules_rust. This skill avoids accidental use ofbazel cleanor non-hermetic commands.
Commands
| Command | Description | Example |
|---|---|---|
| Build target | Build any Bazel label. | bazel build //core/player:player |
| Test target | Run tests for a given target. | bazel test //core/database:database_test |
| Package all | Build distribution packages defined under the package/ directory (AUR, DEB, Flatpak, etc.). | bazel build @pkg//:all |
Usage Guidelines
- Never run
bazel cleanunless explicitly requested by a user; it can invalidate cached outputs and mask real build issues. - Use the
@pkgrepository to trigger packaging for all supported platforms. - For incremental builds, rely on Bazel's caching rather than manual cleaning.
- Never add extra flags or change the platform while building bazel rules unless explicitly specified by the user.
Example Workflow
# Build a core crate
bazel build //core/player:player
# Run tests (aggregated under core_tests at root level)
bazel test //core/database:database_test
# Package all distribution artifacts
bazel build @pkg//:allBzlmod Dependency Management
- All dependencies are managed through
MODULE.bazeland included sub-files undermodules/. - Rust crates: declared in
modules/crates.MODULE.bazelvia thecrates.iointegration. - Toolchains: registered in
modules/rust_toolchains.MODULE.bazel.
Patching External Rules
When patching external rules, always:
- Generate patches via
git diffagainst the clean remote repository commit. - Place patches under
patches/and expose them viaexports_files()in aBUILDfile. - Configure
git_overridewithpatchesandpatch_stripattributes inMODULE.bazel.
© Moosync, 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
Just SKILL.md in .agents/skills/bazel of Moosync/Moosync.
Open the folder on GitHubat commit a2b81ce
Compare with similar skills
Bazel 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 |
|---|---|---|---|---|---|---|
| Bazel this skillMoosync/Moosync | 259 | — | ~722 | Automated safety check: Pass | GPL-3.0 | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Dependency UpdaterAsvarox/allkaraoke | 261 | 4 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Uv Package ManagerYikai-Liao/symusic | 189 | 15 repos | ~4k | Automated safety check: Notes | MIT | |
| Managing Cargo Dependencieshashintel/hash | 1.7k | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 | |
| Next Python Stdlib Upgrade PickerRustPython/RustPython | 22k | — | ~257 | Automated safety check: Pass | MIT |
Similar skills
Dependency Updater
Asvarox/allkaraoke
Smart dependency management for any language. An agent skill from Asvarox/allkaraoke.
Uv Package Manager
Yikai-Liao/symusic
Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows.
Managing Cargo Dependencies
hashintel/hash
Cargo.toml dependency management patterns for HASH workspace.
Next Python Stdlib Upgrade Picker
RustPython/RustPython
Picks the next CPython standard library module ready for a RustPython upgrade, skipping modules that already have an open upgrade pull request.
Dep Auditor
laolaoshiren/claude-code-skills-zh
审计 Node.js、Python、Go、Rust、JVM、Ruby 项目的依赖漏洞、版本健康度与许可证事实；当用户要求检查 package.json、lockfile、requirements、go.mod、Cargo.toml、pom.xml、Gemfile.lock，或生成不改依赖的中文审计报告时使用
More from Moosync/Moosync
Instrumentation
Moosync/Moosync
Hermetic tracing instrumentation rules and validation. An agent skill from Moosync/Moosync.
Moosync
Moosync/Moosync
Project-wide helpers for adding new features to Moosync. An agent skill from Moosync/Moosync.
Rust
Moosync/Moosync
Hermetic Rust crate building, testing, and formatting via Bazel targets.
Slint
Moosync/Moosync
Expert guidance for building, debugging, and working with Slint GUI applications.
Related
Works with
Categories
Questions about Bazel
What does Bazel do?
Hermetic Bazel build, test, and packaging commands for the Moosync project. Bazel is an agent skill from Moosync/Moosync. Hermetic Bazel build, test, and packaging commands for the Moosync project.
When should I use Bazel?
Bazel fits situations like: tasks that involve Dependency management.
How do I install Bazel in Claude Code?
Run `npx skills add Moosync/Moosync --skill bazel -a claude-code`. Or copy the skill folder (.agents/skills/bazel in Moosync/Moosync) into .claude/skills/bazel in your project. Claude Code loads it when a task matches its description.
How do I install Bazel in Codex?
Run `npx skills add Moosync/Moosync --skill bazel -a codex`. Or copy the skill folder (.agents/skills/bazel in Moosync/Moosync) into .agents/skills/bazel in your project. Codex loads it when a task matches its description.
Can I use Bazel 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 Moosync/Moosync --skill bazel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bazel, .gemini/skills/bazel, .github/skills/bazel and .opencode/skills/bazel in your project.
What does Bazel need to run?
Going by SKILL.md and its folder, Bazel needs the command-line tools its instructions call (bazel and git).
Does Bazel access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Bazel 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 Bazel use?
Bazel 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 Bazel use?
About 722 tokens (SKILL.md is roughly 2.9k 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 Bazel?
Skills that share tags, products or a category with Bazel: Pnpm Engine (teambit/bit, 18k stars), Dependency Updater (Asvarox/allkaraoke, 261 stars), Uv Package Manager (Yikai-Liao/symusic, 189 stars) and Managing Cargo Dependencies (hashintel/hash, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bazel?
Moosync (a GitHub organization) maintains it in Moosync/Moosync, which has 259 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 1, 2026.
Source: Moosync/Moosync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.