bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
44
44%
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 ./plugins/developer-essentials/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 build optimization for monorepos) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the 'what' portion could be more specific about the concrete actions it performs beyond the high-level 'optimize' framing.
Suggestions
Expand the capabilities list with more concrete actions, e.g., 'Configure remote caching, write BUILD/BZLMOD files, tune build graph dependencies, set up CI integration with Bazel' to improve specificity.
| 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 'configure caching strategies, set up remote build execution, tune build graph dependencies, write BUILD files'. | 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 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 when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Bazel is a very specific build system, and the combination of 'Bazel', 'monorepo', and 'remote execution' creates a clear niche that is unlikely to conflict with other skills like general CI/CD or other build tool skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
0%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 shallow overview that explains concepts Claude already knows, provides no executable code or concrete commands, lacks any workflow structure, and defers all substantive content to a referenced file that doesn't exist. It fails across all dimensions by being simultaneously verbose about basics and empty of actionable guidance.
Suggestions
Replace the concepts table and directory tree with concrete, executable examples: a working .bazelrc configuration for remote caching, a BUILD.bazel file demonstrating fine-grained targets, and specific bazel commands with flags.
Add a clear multi-step workflow for common tasks like 'Setting up remote caching' with explicit validation steps (e.g., 'Run `bazel build --remote_cache=... //...` and verify cache hits with `--execution_log_json_file`).
Either include the referenced 'references/details.md' as a bundle file with real templates, or inline the most critical templates directly in the SKILL.md.
Remove the 'Key Concepts' table and 'When to Use This Skill' section entirely — Claude knows what Bazel targets and labels are. Use that space for specific configuration patterns and troubleshooting commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill explains basic concepts Claude already knows (what a target, package, label, rule, and aspect are), includes a generic directory tree, and provides a 'When to Use This Skill' section that restates the description. The do's/don'ts are generic advice without actionable specifics. Much of this content wastes tokens on things Claude inherently understands. | 1 / 3 |
Actionability | There is no executable code, no concrete commands, no specific configuration examples, and no copy-paste ready snippets. The entire skill describes concepts abstractly and defers all concrete templates to a referenced file that doesn't exist in the bundle. The do's and don'ts are vague platitudes ('use fine-grained targets', 'pin dependencies') without showing how. | 1 / 3 |
Workflow Clarity | There is no multi-step workflow defined anywhere. For a skill covering remote execution setup, build optimization, migration, and debugging, there are no sequenced steps, no validation checkpoints, and no feedback loops. The content is entirely descriptive with no process guidance. | 1 / 3 |
Progressive Disclosure | The skill references 'references/details.md' for all concrete templates and examples, but no bundle files are provided, meaning the reference leads nowhere. This is effectively a two-level-deep disclosure problem where the main file contains no actionable content and defers everything to a non-existent file. | 1 / 3 |
Total | 4 / 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
- wshobson/agents
- Commit
cf6059d
- 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.