Agent skill

Bazel Build Optimization

Production patterns for Bazel in large monorepos: workspace layout, targets and labels, remote caching and execution, custom rules and build-time tuning.

MITAuto-check passedDevelopment

Install Bazel Build Optimization

skills CLI

$ npx skills add wshobson/agents --skill bazel-build-optimization -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install wshobson/agents bazel-build-optimization --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/developer-essentials/skills/bazel-build-optimization .claude/skills/bazel-build-optimization && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "bazel-build-optimization" agent skill from https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization into .claude/skills/bazel-build-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel-build-optimization", 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

$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization

Type 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.

skills CLI

$ npx skills add wshobson/agents --skill bazel-build-optimization -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wshobson/agents bazel-build-optimization --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/developer-essentials/skills/bazel-build-optimization .agents/skills/bazel-build-optimization && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bazel-build-optimization" agent skill from https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization into .agents/skills/bazel-build-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel-build-optimization", 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.

skills CLI

$ npx skills add wshobson/agents --skill bazel-build-optimization -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wshobson/agents bazel-build-optimization --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/developer-essentials/skills/bazel-build-optimization .cursor/skills/bazel-build-optimization && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bazel-build-optimization" agent skill from https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization into .cursor/skills/bazel-build-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel-build-optimization", 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

$ gemini skills install https://github.com/wshobson/agents.git --path plugins/developer-essentials/skills/bazel-build-optimization

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wshobson/agents --skill bazel-build-optimization -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wshobson/agents bazel-build-optimization --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/developer-essentials/skills/bazel-build-optimization .gemini/skills/bazel-build-optimization && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "bazel-build-optimization" agent skill from https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization into .gemini/skills/bazel-build-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel-build-optimization", 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.

GitHub CLI

$ gh skill install wshobson/agents bazel-build-optimization

Installs 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).

skills CLI

$ npx skills add wshobson/agents --skill bazel-build-optimization -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/developer-essentials/skills/bazel-build-optimization .github/skills/bazel-build-optimization && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "bazel-build-optimization" agent skill from https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization into .github/skills/bazel-build-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel-build-optimization", 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.

skills CLI

$ npx skills add wshobson/agents --skill bazel-build-optimization -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wshobson/agents bazel-build-optimization --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/developer-essentials/skills/bazel-build-optimization .opencode/skills/bazel-build-optimization && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bazel-build-optimization" agent skill from https://github.com/wshobson/agents/tree/main/plugins/developer-essentials/skills/bazel-build-optimization into .opencode/skills/bazel-build-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bazel-build-optimization", 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-build-optimization
GitHub stars: 40k
Used in: 9 other repos
Token cost: ~502 tokens
SKILL.md length: 155 words
Files: 2 (incl. references)
Skills in repo: 142
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Production patterns for Bazel in large monorepos: workspace layout, targets and labels, remote caching and execution, custom rules and build-time tuning.

Works in 2 steps: Bazel Architecture → Key Concepts
Setting up Bazel for a large monorepo
SKILL.md covers When to Use This Skill, Core Concepts, Templates and detailed worked… and Best Practices
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill gives an overview of Bazel for big monorepos: the workspace layout with `WORKSPACE.bazel` and `.bazelrc`, and the core concepts of targets, packages, labels, rules and aspects. It is aimed at setting up Bazel, configuring remote caching and execution, cutting build times, writing custom rules, debugging build problems and migrating to Bazel.

The best-practice list favors fine-grained targets for better caching, pinned dependencies for reproducible builds, remote caching, deliberate visibility to enforce architecture and one BUILD file per directory. It warns against globbing for dependencies, committing the `bazel-*` output directories, skipping workspace setup and ignoring warnings. Templates and worked examples are in `references/details.md`.

When your agent uses it

Setting up Bazel for a large monorepo
Configuring remote caching or remote execution
Cutting build times in a Bazel-based codebase
Writing custom Bazel rules or debugging build failures
Planning a migration to Bazel

Example prompts

“Set up remote caching for our Bazel monorepo and explain what to add to .bazelrc.”
“Split this coarse BUILD target into fine-grained targets so caching works better.”
“Why is our Bazel build slow, and which changes would cut the build time most?”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

Bazel Architecture
Key Concepts

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. 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

Bazel Build Optimization loads about 502 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 155 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~48
When it runs · the whole SKILL.md, loaded when a task matches: ~502
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.4k

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 wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 155 words, ~502 tokens.

Download SKILL.mdSave it as .claude/skills/bazel-build-optimization/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: bazel-build-optimization
description: Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.

Bazel Build Optimization

Production patterns for Bazel in large-scale monorepos.

When to Use This Skill

Setting up Bazel for monorepos
Configuring remote caching/execution
Optimizing build times
Writing custom Bazel rules
Debugging build issues
Migrating to Bazel

Core Concepts

1. Bazel Architecture

workspace/
├── WORKSPACE.bazel       # External dependencies
├── .bazelrc              # Build configurations
├── .bazelversion         # Bazel version
├── BUILD.bazel           # Root build file
├── apps/
│   └── web/
│       └── BUILD.bazel
├── libs/
│   └── utils/
│       └── BUILD.bazel
└── tools/
    └── bazel/
        └── rules/

2. Key Concepts

Concept	Description
Target	Buildable unit (library, binary, test)
Package	Directory with BUILD file
Label	Target identifier `//path/to:target`
Rule	Defines how to build a target
Aspect	Cross-cutting build behavior

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

Use fine-grained targets - Better caching
Pin dependencies - Reproducible builds
Enable remote caching - Share build artifacts
Use visibility wisely - Enforce architecture
Write BUILD files per directory - Standard convention

Don'ts

Don't use glob for deps - Explicit is better
Don't commit bazel-* dirs - Add to .gitignore
Don't skip WORKSPACE setup - Foundation of build
Don't ignore build warnings - Technical debt

Files

SKILL.md and 1 other file (references) in plugins/developer-essentials/skills/bazel-build-optimization of wshobson/agents.

SKILL.md
references/details.md

Open the folder on GitHubat commit 46891e7

Used in 9 other repositories

We found 19 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 9 other GitHub owners. This page covers the copy in wshobson/agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Bazel Build Optimization 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.

Bazel Build Optimization compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bazel Build Optimization this skillwshobson/agents	40k	9 repos	~502	Automated safety check: Pass	MIT	3 days ago
Typescript Expertcin12211/orca-q	224	12 repos	~3.7k	Automated safety check: Pass	MIT	16 days ago
Ckeditor5 ReviewingTriliumNext/Trilium	38k	—	~2.5k	Automated safety check: Pass	AGPL-3.0	today
Mecatl Perf MCP Interpretationstacklok/mecatl	241	—	~2.3k	Automated safety check: Pass	Apache-2.0	today
Pycrazyguitar/pysheeet	8.2k	—	~886	Automated safety check: Pass	MIT	yesterday
Linea Dependency MaintenanceConsensys-Incorporated/linea-attestation-registry	177	1 repos	~3.7k	Automated safety check: Warn	MIT	6 days ago

Similar skills

Typescript Expert
cin12211/orca-q
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
224 GitHub starsUsed in 12 repos~3.7k tokens
DevelopmentAuto-check passed
Ckeditor5 Reviewing
TriliumNext/Trilium
Review or audit CKEditor 5 plugin code in the Trilium (TriliumNext Notes) monorepo, or a PR/diff touching packages/ckeditor5 (including its in-tree plugins under src/plugins/).
38k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Mecatl Perf MCP Interpretation
stacklok/mecatl
Guides reading mecatl's perf MCP data to find why a running harness is slow, leaking goroutines or growing in memory, using cheap reads before any CPU capture.
241 GitHub stars~2.3k tokensUpdated today
DevelopmentAuto-check passed
Py
crazyguitar/pysheeet
Comprehensive Python programming reference covering syntax, concurrency, networking, databases, ML/LLM development, and HPC.
8.2k GitHub stars~886 tokensUpdated yesterday
DevelopmentAuto-check passed
Linea Dependency Maintenance
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…
177 GitHub starsUsed in 1 repo~3.7k tokens
DevelopmentAuto-check: warnings
Dotnet Debugging
novotnyllc/dotnet-artisan
Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…
233 GitHub stars~2.1k tokensUpdated today
DevelopmentAuto-check passed

Questions about Bazel Build Optimization

What does Bazel Build Optimization do?

Production patterns for Bazel in large monorepos: workspace layout, targets and labels, remote caching and execution, custom rules and build-time tuning. bazelrc`, and the core concepts of targets, packages, labels, rules and aspects. It is aimed at setting up Bazel, configuring remote caching and execution, cutting build times, writing custom rules, debugging build problems and migrating to Bazel.

When should I use Bazel Build Optimization?

Bazel Build Optimization fits situations like: setting up Bazel for a large monorepo; configuring remote caching or remote execution; cutting build times in a Bazel-based codebase; writing custom Bazel rules or debugging build failures.

How do I install Bazel Build Optimization in Claude Code?

Run `npx skills add wshobson/agents --skill bazel-build-optimization -a claude-code`. Or copy the skill folder (plugins/developer-essentials/skills/bazel-build-optimization in wshobson/agents) into .claude/skills/bazel-build-optimization in your project. Claude Code loads it when a task matches its description.

How do I install Bazel Build Optimization in Codex?

Run `npx skills add wshobson/agents --skill bazel-build-optimization -a codex`. Or copy the skill folder (plugins/developer-essentials/skills/bazel-build-optimization in wshobson/agents) into .agents/skills/bazel-build-optimization in your project. Codex loads it when a task matches its description.

Can I use Bazel Build Optimization 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 wshobson/agents --skill bazel-build-optimization -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-build-optimization, .gemini/skills/bazel-build-optimization, .github/skills/bazel-build-optimization and .opencode/skills/bazel-build-optimization in your project.

What does Bazel Build Optimization need to run?

SKILL.md names no scripts, command-line tools or credentials: Bazel Build Optimization is instructions for the agent only.

Does Bazel Build Optimization 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 Bazel Build Optimization 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 Build Optimization use?

Bazel Build Optimization is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bazel Build Optimization use?

About 502 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Bazel Build Optimization?

Skills that share tags, products or a category with Bazel Build Optimization: Typescript Expert (cin12211/orca-q, 224 stars), Ckeditor5 Reviewing (TriliumNext/Trilium, 38k stars), Mecatl Perf MCP Interpretation (stacklok/mecatl, 241 stars) and Py (crazyguitar/pysheeet, 8.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bazel Build Optimization?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,287 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Bazel Build Optimization

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bazel Build Optimization

When to Use This Skill

Core Concepts

1. Bazel Architecture

2. Key Concepts

Templates and detailed worked examples

Best Practices

Do's

Don'ts

Files

Used in 9 other repositories

Compare with similar skills

Similar skills

More from wshobson/agents

Related

Questions about Bazel Build Optimization