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
71%
Does it follow best practices?
Impact
97%
1.27xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./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 well-structured skill description with explicit 'Use when' guidance and strong trigger terms specific to the Bazel ecosystem. The main weakness is that the capabilities could be more concrete - listing specific actions like 'write BUILD files', 'configure remote caching', or 'debug dependency issues' would strengthen the specificity dimension.
Suggestions
Add more specific concrete actions such as 'write BUILD files', 'configure remote caching', 'optimize dependency graphs', or 'debug build failures' to improve specificity.
| 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 CI integration'. | 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 | Includes natural keywords 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 | Very distinct niche - Bazel is a specific build system, and the combination with 'monorepo', 'remote execution', and 'enterprise codebases' creates clear, non-conflicting triggers unlikely to overlap with other build tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
52%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 and concrete code examples for Bazel configuration, making it highly practical for implementation. However, it lacks workflow clarity with no sequenced processes or validation checkpoints for complex operations like remote execution setup or migration. The content is somewhat verbose with basic concept explanations and could benefit from better progressive disclosure by moving detailed templates to separate files.
Suggestions
Add explicit multi-step workflows with validation checkpoints, e.g., '1. Configure WORKSPACE -> 2. Validate with bazel build //... -> 3. If errors, check X -> 4. Enable remote caching -> 5. Verify cache hits'
Remove the Core Concepts table explaining basic Bazel terminology (Target, Package, Label, Rule) that Claude already knows
Move detailed templates (WORKSPACE, .bazelrc, BUILD files) to separate reference files and keep only quick-start examples in the main skill
Add verification commands after each major configuration step, such as 'bazel info' to confirm settings or test builds to validate configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably 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 knows. The templates are comprehensive but could be more focused. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples including complete WORKSPACE configuration, .bazelrc settings, BUILD files for TypeScript and Python, custom rules, and query commands. All templates are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Despite being about build optimization, there are no clear multi-step workflows with validation checkpoints. The skill presents templates and commands but lacks sequenced processes like 'configure -> validate -> optimize -> verify'. No feedback loops for error recovery in build configuration. | 1 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples but the main content is a monolithic document with extensive inline templates. The structure exists (sections, templates) but much content could be split into separate reference files for better organization. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.