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

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

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 builds 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 general 'optimize' verb. Overall it performs well for skill selection purposes.

Suggestions

Expand the capabilities list with more concrete actions, e.g., 'write BUILD files, configure remote caching, tune build graph dependencies, set up CI integration' 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 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 when seeking help.	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 general 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 a verbose collection of Bazel templates and boilerplate rather than a focused optimization guide. It lacks a coherent workflow for diagnosing and improving build performance, which is its stated purpose. The templates are concrete but generic, and the skill would benefit greatly from being restructured as a concise overview with referenced detail files and a clear optimization workflow with validation steps.

Suggestions

Restructure as a concise overview (under 80 lines) that defines a clear optimization workflow: profile → identify bottlenecks → apply specific fixes → validate improvement, with explicit checkpoints.

Move the lengthy templates (WORKSPACE, BUILD files, .bazelrc, custom rules) into separate bundle files and reference them from the main skill with one-line descriptions of when each applies.

Remove the 'Key Concepts' table and basic architecture diagram — Claude already knows Bazel fundamentals. Focus token budget on non-obvious optimization patterns and decision criteria.

Add concrete validation steps: e.g., 'After enabling remote caching, verify cache hits with `bazel build //... --remote_cache_hit_rate` and expect >80% on second build.'

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive template code that Claude already knows how to produce. The key concepts table explains basic Bazel terminology (Target, Package, Label) that Claude already understands. The WORKSPACE configuration, BUILD files, and .bazelrc templates are largely boilerplate that inflate token count without adding unique optimization insight. The skill is ~300+ lines when it could convey the same actionable value in under 80.	1 / 3
Actionability	The templates provide concrete, copy-paste-ready code examples (WORKSPACE, BUILD files, .bazelrc, query commands), which is good. However, much of it is generic boilerplate rather than optimization-specific guidance. The 'Performance Optimization' section has useful commands but lacks interpretation of results or decision criteria. The instructions section ('Clarify goals, constraints, and required inputs') is vague and not actionable.	2 / 3
Workflow Clarity	There is no clear multi-step workflow for build optimization. The skill presents disconnected templates and tips without sequencing them into a coherent process. For a skill about optimizing builds in large monorepos, there are no validation checkpoints, no feedback loops for profiling->fixing->re-profiling, and no guidance on when to apply which optimization. The performance profiling section lists commands but doesn't explain what to do with the results.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed examples, which is good progressive disclosure intent. However, no bundle files are provided, so that reference is unverifiable. The main file itself is a monolithic wall of templates that should have been split into separate reference files (e.g., templates in one file, query cheatsheet in another), with the SKILL.md serving as a concise overview.	2 / 3
	Total	6 / 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: 9d0b37c

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