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. The main weakness is that the specificity of concrete actions could be improved by listing more granular capabilities beyond the high-level 'optimize' and 'configure'.
Suggestions
Expand the 'what' portion with more concrete actions, e.g., 'Configure remote caching, write BUILD/WORKSPACE files, tune build graph dependencies, set up CI integration for Bazel builds.'
| 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, 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' (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 a developer working with Bazel would naturally use. | 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 CI/CD 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.
This skill provides extensive, concrete Bazel configuration templates but suffers from being a large, monolithic reference dump rather than an actionable guide. It explains basic concepts Claude already knows, lacks any workflow sequencing or validation steps for what is inherently a multi-step configuration process, and would benefit greatly from splitting content into focused reference files with a concise overview.
Suggestions
Remove the 'Key Concepts' table and basic architecture explanation—Claude knows what Bazel targets, packages, and labels are. This alone would save ~20 lines.
Add a clear workflow section with sequenced steps for setting up Bazel in a monorepo (e.g., 1. Create WORKSPACE → 2. Configure .bazelrc → 3. Validate with `bazel build //...` → 4. Add remote caching), including validation checkpoints after each step.
Split the templates into separate referenced files (e.g., WORKSPACE_SETUP.md, REMOTE_EXECUTION.md, CUSTOM_RULES.md) and keep SKILL.md as a concise overview with navigation links.
Add verification/validation commands after each template (e.g., 'Run `bazel build //...` to verify WORKSPACE setup' or 'Test remote cache with `bazel build --config=remote-cache //libs/utils:utils`').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300 lines, with significant padding. The 'Key Concepts' table explains what targets, packages, labels, and rules are—concepts Claude already knows. The WORKSPACE template includes version-specific URLs and SHA placeholders that add bulk without value. Multiple full templates could be condensed significantly. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready code across multiple languages and configurations. BUILD files, .bazelrc settings, custom rules, and query commands are all concrete and complete with real syntax. | 3 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequencing. Templates are presented as isolated blocks without guidance on order of operations, validation checkpoints, or error recovery. For a skill involving build system configuration (which can be destructive/complex), there are no feedback loops or verification steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of templates with no separation into referenced files. The remote execution setup, custom rules, and query commands could each be separate reference files. External links at the bottom are generic documentation links, not structured navigation to bundled content. | 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
bbc5ade
- 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.