bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
80
Quality
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/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 optimization for enterprise monorepos) and provides explicit trigger guidance. The main weakness is that the 'what' portion could be more specific about concrete actions beyond the general 'optimize' verb. The description effectively uses third person voice and includes domain-specific terminology that users would naturally employ.
Suggestions
Expand specificity by listing concrete actions like 'write BUILD files, configure remote caching, set up sandboxing, debug dependency graphs'
Add file extension triggers like '.bazel', 'BUILD.bazel', 'WORKSPACE' to improve matching on file-based queries
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bazel builds, monorepos) and some actions (configuring, implementing remote execution, optimizing), but lacks comprehensive specific actions like 'write BUILD files', 'configure caching', or 'set up sandboxing'. | 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') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Bazel', 'monorepo', 'remote execution', 'build performance', 'enterprise codebases'. These are terms developers naturally use when seeking Bazel help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - Bazel is a specific build system, and terms like 'remote execution', 'monorepo', and 'enterprise codebases' create a well-defined scope unlikely to conflict with general build or CI/CD skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable templates for Bazel configuration with production-ready code examples covering WORKSPACE, .bazelrc, BUILD files, and custom rules. However, it lacks clear sequential workflows with validation checkpoints for setup processes, and could be more concise by moving detailed templates to referenced files and removing basic concept explanations.
Suggestions
Add a clear step-by-step workflow for initial Bazel setup with validation checkpoints (e.g., 'Run bazel info to verify installation', 'Test remote cache with bazel build --config=remote-cache //test:target')
Move detailed templates (WORKSPACE, .bazelrc, BUILD examples) to separate reference files and keep only quick-start examples in the main skill
Remove the Core Concepts table explaining basic Bazel terminology (Target, Package, Label, Rule) as Claude already knows these
Add troubleshooting steps with specific error messages and fixes for common Bazel issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary content like the 'Do not use this skill when' section stating obvious non-applicability, and the Core Concepts table explains basic Bazel terminology that Claude likely already knows. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready templates for WORKSPACE, .bazelrc, BUILD files, custom rules, and query commands. Code examples are complete and production-ready with real package names and configurations. | 3 / 3 |
Workflow Clarity | While templates are well-organized, there's no clear sequential workflow for setting up Bazel from scratch. Missing validation checkpoints - for example, no steps to verify remote cache connectivity or validate BUILD file syntax before proceeding. | 2 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples but the main file is quite long (~300 lines) with extensive templates that could be split into separate reference files. The structure is reasonable but content that could be external is inline. | 2 / 3 |
Total | 9 / 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
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.