bazel-build-optimization

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

1.27x

Quality

52%

Does it follow best practices?

Impact

97%

1.27x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/bazel-build-optimization/SKILL.md

Quality

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) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capability description could be more specific—listing concrete actions like configuring remote caching, writing BUILD files, debugging dependency graphs, or tuning build parallelism would strengthen it.

Suggestions

Expand the 'what' portion with more concrete actions, e.g., 'configure remote caching, write BUILD/WORKSPACE files, debug dependency graphs, tune parallelism and memory settings'.

Add a few more trigger term variations such as 'BUILD files', 'WORKSPACE', 'Starlark', 'bazelrc', 'build cache' to improve keyword coverage.

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 remote caching, set up build rules, debug dependency graphs, tune worker pools'.	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 for enterprise codebases) 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.	3 / 3
Distinctiveness Conflict Risk	Bazel is a very specific build system, and the combination of 'Bazel', 'monorepo', 'remote execution', and 'enterprise codebases' creates a clear niche that is unlikely to conflict with other build tool or CI/CD skills.	3 / 3
	Total	11 / 12 Passed

Implementation

14%

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

This skill reads more like a Bazel reference cheat sheet than an actionable skill for Claude. It is excessively verbose with inlined templates and concept explanations that Claude already knows, while lacking the most important elements: clear workflows, validation steps, and decision-making guidance. The instructions section is generic and unhelpful, and the content would benefit enormously from being restructured into a concise overview with references to separate template/reference files.

Suggestions

Move the seven templates into a separate file (e.g., resources/templates.md) and replace them with a concise summary table linking to each template with a one-line description of when to use it.

Remove the 'Key Concepts' table and basic architecture diagram—Claude knows what Bazel targets, packages, and labels are. Focus only on project-specific conventions or non-obvious patterns.

Add a clear multi-step workflow for the primary use cases (e.g., 'Setting up Bazel for a new monorepo': step 1 → step 2 → validate → step 3) with explicit validation checkpoints like 'Run `bazel build //...` to verify configuration before proceeding'.

Replace the vague instructions ('Apply relevant best practices and validate outcomes') with specific decision trees or conditional guidance (e.g., 'If remote caching is needed, configure X; if local-only, configure Y').

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines, with significant content Claude already knows (key concepts table explaining what a 'Target' or 'Label' is, basic Bazel architecture). The 'Do not use this skill when' section is trivially obvious. Multiple full templates are inlined that should be in separate reference files.	1 / 3
Actionability	The templates provide concrete, copy-paste-ready code examples for WORKSPACE, .bazelrc, BUILD files, and queries, which is good. However, much of it is boilerplate with placeholder values (sha256='...', grpcs://cache.example.com) and lacks guidance on adapting templates to specific situations. The instructions section is vague ('Apply relevant best practices and validate outcomes').	2 / 3
Workflow Clarity	There is no clear multi-step workflow or sequenced process. The instructions are four vague bullet points ('Clarify goals, constraints, and required inputs'). For a skill involving build system configuration—where misconfiguration can break builds—there are no validation checkpoints, no feedback loops, and no error recovery guidance. The profiling commands are listed without explaining when to use them or what to do with results.	1 / 3
Progressive Disclosure	The skill is a monolithic wall of text with seven full templates inlined. It references 'resources/implementation-playbook.md' once but dumps hundreds of lines of templates that should be in separate files. There's no clear navigation structure—it's essentially a reference dump rather than an overview with signposted deeper resources.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 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: sickn33/antigravity-awesome-skills
Commit: 43280f9

Reviewed: 2 days 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.