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

74%

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

61%Weight 40%Scale 1-5

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

The body is highly actionable with copy-paste-ready Bazel examples, but it is weighed down by inlined templates that belong in separate files, a broken reference, basic-concept over-explanation, and a generic workflow section lacking concrete validation checkpoints.

Suggestions

Split the seven inlined templates into separate files under resources/ (e.g., templates/workspace.bzl, templates/bazelrc) and link to them from SKILL.md, fixing the broken `resources/implementation-playbook.md` reference.

Replace the generic 'Instructions' bullets with a concrete sequenced workflow including an explicit validation checkpoint (e.g., 'bazel build //... && bazel test //...') and an error-recovery feedback loop for migrations and custom-rule authoring.

Remove or condense the 'Core Concepts' table explaining basic Bazel terms, and move time-sensitive version pins (rules_js, node, rules_python) into a separate versioned/deprecated section so they don't penalize the core reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference material, but the 'Core Concepts' table explains basic Bazel terms (Target, Package, Label) Claude likely knows, and time-sensitive version pins (rules_js-1.34.0, node 20.9.0) sit inline rather than in a deprecated section. Not 4 because these are more than minor trimmable bits; not 2 because the bulk is genuinely useful executable reference rather than padded prose.	3 / 5
Actionability	Provides fully executable, copy-paste-ready WORKSPACE, .bazelrc, BUILD, custom-rule, and bazel-query examples covering the common cases. Not 4 because the guidance is comprehensive rather than having only minor gaps.	5 / 5
Workflow Clarity	The 'Instructions' section gives generic steps ('Clarify goals', 'apply best practices and validate outcomes') with no concrete sequence or validation checkpoint for risky operations like migration or custom-rule authoring. Capped at 3 per the rubric: destructive/batch workflows without concrete validation cannot exceed 3. Not 4 because validation is implicit and abstract rather than explicit checkpoints.	3 / 5
Progressive Disclosure	No bundle files exist and the one signaled reference, `resources/implementation-playbook.md`, is a broken path (file missing), while seven full templates are inlined into SKILL.md that clearly belong in separate reference files. Not 3 because the broken reference and inlined bulk pull it below 'some structure'; not 1 because section headers do provide navigable structure.	2 / 5
	Total	13 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong description that clearly states what the skill does and when to use it, with concrete trigger phrases and a well-scoped niche. Minor gains are possible by adding common synonyms and file-extension terms (e.g., '.bazel', 'BUILD files').

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'configuring Bazel', 'implementing remote execution', 'optimizing build performance' — with only minor coverage gaps (custom rules, migration are absent). Not 5 because the action list is not comprehensive, and not 3 because it names more than 1-2 specific actions.	4 / 5
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') with concrete trigger phrases. Not 4 because the 'when' clause is explicit and specific rather than merely adequate.	5 / 5
Trigger Term Quality	Good natural-term coverage including 'Bazel', 'remote execution', 'build performance', and 'monorepos', but missing common synonyms and file extensions a user might say ('.bazel', 'BUILD files', 'build times'). Not 5 because it lacks comprehensive synonym/extension coverage, not 3 because keyword coverage is clearly strong.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche ('Bazel builds for large-scale monorepos' with remote execution triggers) that is unlikely to fire for unrelated skills. Not 4 because the triggers are distinctively Bazel-specific with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/bazel-build-optimization/SKILL.md
Commit: 1f67c44

Reviewed: about 16 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.