bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill bazel-build-optimizationOverall
score
72%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
90%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 'Use when' guidance. The main weakness is that the specific capabilities could be more detailed - listing concrete actions like writing BUILD files, configuring remote caching, or debugging build graphs would strengthen the description.
Suggestions
Expand specific actions to include concrete tasks like 'write BUILD files', 'configure remote caching', 'debug dependency graphs', or 'set up CI pipelines'
| 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 | 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 skills. | 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 concrete templates and executable code for Bazel configuration, making it highly actionable. However, it lacks workflow clarity with no validation steps or debugging workflows for complex build operations, and the document is overly long with templates that should be in separate referenced files. The generic 'Instructions' section adds no value and the skill would benefit from clear step-by-step processes for common tasks like setting up remote caching.
Suggestions
Add explicit multi-step workflows with validation checkpoints, e.g., '1. Configure .bazelrc 2. Run `bazel build //...` to verify 3. If errors, check X 4. Enable remote cache only after local builds succeed'
Move the extensive templates (WORKSPACE, BUILD files, custom rules) to separate referenced files like `templates/workspace.md` and keep only quick-start examples in the main skill
Replace the generic 'Instructions' section with specific troubleshooting workflows for common issues like cache misses, remote execution failures, or dependency conflicts
Remove the 'Core Concepts' table explaining basic Bazel terminology (Target, Package, Label) that Claude already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose with extensive templates that could be referenced externally. The 'Core Concepts' table explains basic Bazel terminology Claude likely knows, and some templates are overly detailed for an overview document. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples including complete WORKSPACE configurations, BUILD files, .bazelrc settings, and bash commands for queries. 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 'Instructions' section is vague ('Apply relevant best practices and validate outcomes'), and there's no guidance on verifying builds work correctly or debugging failed configurations. | 1 / 3 |
Progressive Disclosure | References `resources/implementation-playbook.md` for detailed examples, but the main document itself is a monolithic wall of templates that could be split into separate files. The structure exists but content that should be in referenced files is inline. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.