bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
48
52%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 solid skill description that clearly identifies its niche (Bazel builds in monorepos) and provides explicit trigger guidance. The main weakness is that the 'what' portion could be more specific about concrete actions (e.g., writing BUILD files, configuring remote caching, setting up sandboxed execution). The trigger terms and distinctiveness are strong given Bazel's specificity as a tool.
Suggestions
Expand the capability list with more concrete actions, e.g., 'writing BUILD/WORKSPACE files, configuring remote caching, setting up toolchains, debugging dependency graphs'.
| 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 writing BUILD files, setting up caching, configuring toolchains, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize Bazel builds for large-scale monorepos) and 'when' (configuring Bazel, implementing remote execution, optimizing build performance) 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 + remote execution creates a clear niche that is unlikely to conflict with other build tool or CI/CD 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 essentially a Bazel template catalog dumped into a single file, lacking workflow structure, decision guidance, and proper progressive disclosure. It explains basic concepts Claude already knows while failing to provide the actionable sequencing and validation steps needed for complex build system operations. The content would benefit enormously from restructuring into a concise overview with referenced template files and clear step-by-step workflows for each use case.
Suggestions
Replace the monolithic template dump with a concise overview and move templates into separate referenced files (e.g., templates/workspace.md, templates/bazelrc.md) for proper progressive disclosure.
Add explicit multi-step workflows with validation checkpoints for key use cases like 'Setting up Bazel for a new monorepo' or 'Migrating to Bazel' (e.g., Step 1: Create WORKSPACE → Step 2: Validate with `bazel build //...` → Step 3: If errors, check X).
Remove the Key Concepts table and basic Bazel architecture explanation—Claude already knows these. Focus tokens on non-obvious patterns, gotchas, and decision criteria.
Make the instructions section actionable by replacing vague guidance ('Apply relevant best practices') with specific decision trees (e.g., 'If monorepo has >100 packages, enable remote caching first; if <100, start with disk cache').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive template code that Claude already knows how to produce. The key concepts table explains basic Bazel terminology (Target, Package, Label) that Claude already understands. Multiple full template files are inlined that could be referenced externally or generated on demand. | 1 / 3 |
Actionability | The templates provide concrete, executable code examples for WORKSPACE, BUILD files, .bazelrc, and queries, which is good. However, the skill reads more like a reference catalog than actionable guidance—it lacks clear decision logic for when to apply which template, and the instructions section is vague ('Apply relevant best practices and validate outcomes'). | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow for any of the stated use cases (setting up Bazel, migrating to Bazel, optimizing builds). The templates are presented as isolated blocks without sequencing, validation checkpoints, or feedback loops. For a skill involving build system configuration—where misconfigurations can cascade—the absence of verification steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` but no bundle files are provided, making this a dead reference. All content is inlined as a monolithic wall of templates with no meaningful structure for navigation. The massive template blocks should be split into separate referenced files. | 1 / 3 |
Total | 5 / 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
fb2efea
- 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.