bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
59
Quality
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/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
22%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 hollow shell that delegates everything to sub-skills without providing any actionable content in the main file. The instructions are generic boilerplate that could apply to any skill, and there's no Bazel-specific guidance, code examples, or workflows. The progressive disclosure structure exists but fails because the main file offers no value on its own.
Suggestions
Add a Quick Start section with at least one executable Bazel command or minimal BUILD file example
Replace generic instructions ('Apply relevant best practices') with Bazel-specific guidance like common bazel build/test commands
Add brief descriptions to each sub-skill link explaining what problem it solves and when to use it
Include a basic workflow for common tasks like 'Setting up a new Bazel project' with numbered steps and validation commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary sections like 'Do not use this skill when' with obvious statements, and the instructions are generic boilerplate rather than Bazel-specific guidance. | 2 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The instructions are entirely abstract ('Apply relevant best practices', 'Provide actionable steps') with no Bazel-specific guidance in the main file. | 1 / 3 |
Workflow Clarity | No workflow is defined despite the skill covering complex multi-step processes like remote execution setup and build optimization. The instructions are generic placeholders with no sequencing or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills appropriately with one-level-deep links, but the main file provides almost no useful overview content - it's essentially just a table of contents with no quick-start guidance or context for when to use which sub-skill. | 2 / 3 |
Total | 6 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.