bazel-build-optimization

Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bazel-build-optimization/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Strong on actionability with abundant executable Bazel templates and commands, but the skill is a monolithic single-file dump with limited workflow sequencing and no progressive disclosure via bundle files.

Suggestions

Move the longer templates (WORKSPACE, .bazelrc, custom rules) into reference files and link to them from SKILL.md so the body stays a lean overview.

Replace the Key Concepts table of generic Bazel terms (Target/Package/Label/Rule/Aspect) with content Claude doesn't already know, or remove it to save tokens.

Add explicit sequenced workflows with validation checkpoints for risky operations such as remote execution setup and remote caching (e.g., validate config -> run small build -> inspect profile -> scale up).

Dimension	Reasoning	Score
Conciseness	Templates are code-heavy and assume Bazel knowledge with little padding, but the body is ~390 lines and includes a Key Concepts table explaining Target/Package/Label/Rule/Aspect — concepts Claude largely already knows.	2 / 3
Actionability	Provides multiple concrete, executable, copy-paste-ready artifacts: WORKSPACE and .bazelrc configs, BUILD files, a custom Starlark rule, and bazel query commands.	3 / 3
Workflow Clarity	Content is organized as loose command/template catalogs rather than sequenced multi-step workflows, and there are no explicit validation checkpoints or feedback loops for risky operations like remote execution setup or custom rule development.	2 / 3
Progressive Disclosure	Everything lives in a single ~390-line SKILL.md with no bundle files (no references/scripts/assets); content that could be split out (templates, reference) is inline rather than signaled via one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

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.

A clear, well-scoped description with explicit 'what' and 'when' guidance and good natural trigger terms. The only weakness is that 'optimize' is a broad action verb rather than a list of several distinct concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ('configuring Bazel', 'implementing remote execution', 'optimizing build performance'), but 'optimize' is broad rather than a list of multiple distinct concrete actions.	2 / 3
Completeness	Explicitly answers both what ('Optimize Bazel builds for large-scale monorepos') and when ('Use when configuring Bazel, implementing remote execution, or optimizing build performance').	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'Bazel builds', 'large-scale monorepos', 'remote execution', 'build performance', 'enterprise codebases' — with good variation.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Bazel build optimization for enterprise monorepos) with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/bazel-build-optimization/SKILL.md
Commit: e63f7dd

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.