Guide · Agent skill
How to use the Bazel Build Optimization agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The bazel-build-optimization skill is a set of written guidance that teaches an AI agent common Bazel patterns for large monorepos, including workspace layout, fine-grained targets, remote caching, remote execution and debugging build problems. This guide explains what the skill does, how to install it, how to ask for help with natural requests, and what to check before trusting the output. By the end you will know how to add the skill to Claude and get useful Bazel suggestions from it.
Bazel Build Optimizationwshobson/agents · MIT Download the skill Quick start
- 1Download the skill ZIP. Get the bazel-build-optimization ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ in a project for project use.
- 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Ask a Bazel question. Describe your monorepo, cache or build problem in plain language that mentions Bazel.
- 5Test suggestions in Bazel. Run any suggested configuration or commands in a real Bazel install before relying on them.
What the Bazel Build Optimization skill makes the agent do
Once installed, the agent knows Bazel patterns aimed at large codebases. The skill covers how to lay out workspace files such as WORKSPACE.bazel, .bazelrc and BUILD.bazel files, how to use fine-grained build targets, how to set up remote caching and remote execution, and how to debug build issues.
The skill is guidance only. It does not build, test or change your project by itself. When the agent needs concrete code, it reads references/details.md, which holds templates and worked examples.
- Workspace and BUILD file layout for monorepos
- Fine-grained targets and the Bazel concepts of target, package, label, rule and aspect
- Remote caching and remote execution setup
- Debugging build problems
- Migrating an existing project to Bazel
How to install the skill in Claude
You can install the skill for yourself or for a single project. For a personal install, download the skill ZIP from the page, unzip it and place the folder in ~/.claude/skills/. For a project install, place it in the .claude/skills/ folder inside your project.
If you use the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal: unzip into ~/.claude/skills/
- Per project: unzip into .claude/skills/ in the project root
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
How to trigger the skill with a natural request
You do not need a special command. Describe the task in plain language that mentions Bazel, remote execution, or build performance. The skill's description tells the agent when to use it, so requests about configuring Bazel, implementing remote execution or speeding up enterprise builds are the ones that match.
Include details that help the agent answer well, such as how many packages you have, which languages are involved and what is slow.
- Set up Bazel for a monorepo with about the number of packages I have, using one BUILD file per directory.
- Help me configure remote caching for Bazel and explain what to put in .bazelrc.
- Our Bazel builds are slow in CI. Suggest changes to targets and caching to speed them up.
- Migrate this project from another build system to Bazel and outline the workspace layout.
What to check before you rely on the output
The skill supplies guidance, and the output still needs testing against a real Bazel install. Run any suggested commands yourself and confirm the results. Review any template that includes placeholder values, such as the empty sha256 fields in the example WORKSPACE template, and fill in real values before use.
The skill's own best practices say to pin dependencies, avoid glob for dependencies, keep bazel-* output directories out of git, and not ignore build warnings.
- Install Bazel and run suggested commands in a test checkout first
- Replace placeholder values in templates with real ones
- Verify remote cache or remote execution settings with your service provider
What people use it for
- Laying out WORKSPACE.bazel, .bazelrc and BUILD.bazel files for a new monorepo
- Splitting large targets into finer-grained targets to improve caching
- Setting up remote caching to share build artifacts across a team
- Working through a Bazel build error with the agent's debugging guidance
- Planning a migration of an existing project to Bazel
Frequently asked questions
How do I install the bazel-build-optimization skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ in your project. In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills instead.
Is the bazel-build-optimization skill free?
The skill is published under the MIT licence. Check the licence file in the source repository for the full terms before reusing it.
What do I need to use this skill?
You need the Bazel build tool for any code you run, and a remote cache or remote execution service if you use those features. The skill itself runs no scripts and uses no network access.
Does the skill run Bazel builds for me?
No. The skill only supplies guidance. You must run and test any commands or configuration in your own Bazel install.
Is this skill useful for a small project?
Probably not. The skill is aimed at large monorepos, and Bazel's setup overhead is not worth it for small single-package projects.
How is this different from just asking the agent about Bazel?
The skill packages Bazel patterns for large codebases and a reference file of templates and worked examples that the agent reads when it needs concrete code. Without it, the agent relies on general knowledge alone.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits engineers setting up Bazel for a large monorepo, teams trying to cut build and test times with remote caching, and developers migrating an existing project to Bazel. Skip it for small single-package projects, or if you expect it to run builds or verify results automatically, since it only gives guidance you must test yourself.
Download the skill