bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
73
59%
Does it follow best practices?
Impact
94%
1.34xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/bazel-build-optimization/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Bazel build optimization) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capability description could be more specific about the concrete actions it performs (e.g., writing BUILD files, configuring remote caching, setting up CI pipelines, debugging dependency graphs).
Suggestions
Expand the 'what' portion with more concrete actions, e.g., 'write BUILD files, configure remote caching, debug dependency graphs, set up toolchains' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bazel builds, monorepos) and some actions (configuring, implementing remote execution, optimizing build performance), but doesn't list multiple concrete specific actions like writing BUILD files, setting up caching, configuring toolchains, etc. | 2 / 3 |
Completeness | Clearly answers both what ('Optimize Bazel builds for large-scale monorepos') and when ('Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Bazel', 'monorepo', 'remote execution', 'build performance', 'enterprise codebases'. These are terms developers naturally use when seeking help with Bazel optimization. | 3 / 3 |
Distinctiveness Conflict Risk | Bazel is a very specific build system, and the combination of 'Bazel', 'monorepo', and 'remote execution' creates a clear niche that is unlikely to conflict with other build tool skills or general coding skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides high-quality, executable Bazel configuration templates that are immediately usable, which is its primary strength. However, it is severely bloated—inlining hundreds of lines of templates that should be progressively disclosed via separate files. It lacks any workflow structure, presenting reference material without guiding Claude through sequenced processes with validation steps, and it explains basic Bazel concepts that Claude already knows.
Suggestions
Extract the 7 templates into separate referenced files (e.g., templates/workspace.md, templates/bazelrc.md) and keep only a concise overview with links in SKILL.md.
Remove the 'Key Concepts' table and 'When to Use This Skill' section—Claude already knows what Bazel targets, packages, and labels are.
Add a clear multi-step workflow for common tasks like 'Setting up Bazel for a new monorepo' or 'Optimizing an existing build' with explicit validation checkpoints (e.g., verify remote cache connectivity, validate build graph, confirm cache hit rates).
Add a debugging/validation workflow: profile build → identify bottleneck → apply fix → re-profile → verify improvement, rather than just listing profiling commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It includes a concept table explaining what targets, packages, labels, rules, and aspects are—things Claude already knows. The 'When to Use This Skill' section and 'Core Concepts' section add little value. Multiple full templates are inlined when they could be referenced separately. | 1 / 3 |
Actionability | The templates provide fully executable, copy-paste ready code for WORKSPACE files, .bazelrc, BUILD files, custom rules, and bazel query commands. The code is concrete and specific with real package names and realistic configurations. | 3 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequenced process. The skill presents templates and reference material but never guides through a process like 'set up Bazel for a monorepo' with ordered steps and validation checkpoints. Performance profiling commands are listed without a workflow for interpreting results or iterating on fixes. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all templates inlined. Seven full templates plus performance commands and best practices are all in one file with no references to separate files. The WORKSPACE config, .bazelrc, multiple BUILD files, and custom rules should be split into referenced documents. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.