bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
78
52%
Does it follow best practices?
Impact
95%
1.15xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/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 for monorepos) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capability listing could be more granular—specifying concrete actions like writing BUILD files, configuring remote caching, or setting up build rules would strengthen it further.
Suggestions
Expand the capability list with more concrete actions, e.g., 'write BUILD files, configure remote caching, optimize dependency graphs, set up build rules and toolchains'.
| 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 'configure caching strategies, set up remote execution, tune build graph dependencies, write BUILD files'. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize Bazel builds for large-scale monorepos) and 'when' with an explicit 'Use when...' clause covering configuring Bazel, implementing remote execution, and optimizing build performance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Bazel', 'monorepo', 'remote execution', 'build performance', 'enterprise codebases'. These are terms a developer working with Bazel would naturally use in requests. | 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 skills like general CI/CD or other build tool skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a Bazel reference/cheat sheet than an actionable optimization guide. It is excessively verbose, explains concepts Claude already knows, and lacks any coherent workflow for the stated goals of optimizing builds or migrating to Bazel. The templates are useful but disconnected, with no sequencing, validation steps, or progressive disclosure.
Suggestions
Add a clear multi-step workflow for the primary use cases (e.g., 'Setting up remote caching: 1. Configure .bazelrc → 2. Verify cache hits with --remote_cache_hit_rate → 3. Debug misses with --execution_log_json_file') with explicit validation checkpoints.
Remove the Key Concepts table and directory tree—Claude knows basic Bazel terminology. Cut the content by at least 50% by focusing only on non-obvious patterns and decisions.
Split into a concise SKILL.md overview with quick-start essentials, and reference separate files for templates (e.g., WORKSPACE_SETUP.md, REMOTE_EXECUTION.md, CUSTOM_RULES.md).
Replace placeholder values (sha256='...', 'cache.example.com') with either real working examples or explicit instructions on how to obtain the correct values.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with significant padding. The 'Key Concepts' table explains basic Bazel terminology (targets, packages, labels) that Claude already knows. The workspace directory tree, concept table, and extensive template code could be dramatically condensed. Version-specific URLs and sha256 placeholders add bulk without value. | 1 / 3 |
Actionability | The templates provide concrete, mostly executable code examples for WORKSPACE, .bazelrc, BUILD files, and custom rules. However, many are incomplete (sha256='...', placeholder URLs like 'cache.example.com'), and the custom Docker rule references a non-existent '//tools/docker:builder' without explanation. The query commands in Template 6 are genuinely useful and copy-paste ready. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequenced process. The skill presents isolated templates without connecting them into a coherent setup or optimization workflow. For a skill about 'optimizing builds' and 'migrating to Bazel,' there are no validation checkpoints, no feedback loops for debugging build issues, and no sequenced steps for the profiling/optimization process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of templates with no references to external files or layered organization. All content—from basic setup to remote execution to custom rules—is dumped inline. There's no separation between quick-start essentials and advanced topics, and no pointers to supplementary materials. | 1 / 3 |
Total | 5 / 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
- wshobson/agents
- Commit
27a7ed9
- 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.