bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
67
52%
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 with clear 'what' and 'when' clauses and strong domain-specific trigger terms. Its main weakness is that the capability listing could be more granular—specifying concrete actions like writing BUILD files, configuring caching, or setting up sandboxing would strengthen it. Overall it performs well for skill selection purposes.
Suggestions
Expand the specificity by listing more concrete actions, e.g., 'write BUILD/WORKSPACE files, configure remote caching, set up sandboxed execution, optimize dependency graphs, troubleshoot build failures'.
| 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 is a large collection of Bazel configuration templates and commands but suffers from verbosity, lack of workflow structure, and poor progressive disclosure. It explains concepts Claude already knows, presents templates without clear sequencing or validation steps, and dumps everything into a single monolithic file. The actionability is moderate—templates are concrete but not truly production-ready due to placeholders and missing context.
Suggestions
Remove the 'Key Concepts' table and 'When to Use This Skill' section—Claude already knows what Bazel targets, packages, and labels are. Replace with a brief 'Quick start' workflow.
Add a clear multi-step workflow with validation checkpoints, e.g.: 1. Set up WORKSPACE → 2. Verify with `bazel build //...` → 3. Configure .bazelrc → 4. Validate remote cache connectivity → 5. Run full build and check profile.
Split the monolithic content into separate referenced files (e.g., WORKSPACE_SETUP.md, REMOTE_EXECUTION.md, CUSTOM_RULES.md) and keep SKILL.md as a concise overview with links.
Replace placeholder values (sha256='...', grpcs://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 what targets, packages, labels, and rules are—concepts Claude already knows. The 'Core Concepts' section, 'When to Use This Skill' list, and 'Best Practices' do's/don'ts are largely things Claude would already understand. Version-specific URLs with placeholder sha256 values add bulk without real utility. | 1 / 3 |
Actionability | The templates provide concrete, mostly executable Bazel configurations and commands, which is good. However, many templates are boilerplate with placeholder values (sha256='...', grpcs://cache.example.com) that aren't truly copy-paste ready. The custom Docker rule references a non-existent //tools/docker:builder. The skill describes patterns but doesn't give clear guidance on when to choose between approaches or how to diagnose specific problems. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow with sequencing or validation checkpoints. The templates are presented as isolated snippets without a coherent process for setting up, validating, or iterating on a Bazel configuration. For a skill involving build system configuration (which can be destructive/complex), the absence of any validation steps or feedback loops is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of templates and configuration snippets all inline, with no separation into referenced files. The external links at the bottom are generic documentation links, not structured references to companion files. A skill this large should split templates into separate files (e.g., WORKSPACE_SETUP.md, REMOTE_EXECUTION.md) with a concise overview in the main file. | 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
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.