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

64%

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

47%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 delivers strong, concrete reference material — executable configs, BUILD templates, and a custom rule — but reads as a template dump rather than a skill. It lacks any sequenced optimization workflow with validation checkpoints, pads itself with boilerplate and beginner-concept explanations, and inlines bulk content that should live in separate files while pointing to a reference file that is missing.

Suggestions

Replace the abstract Instructions with a concrete diagnostic workflow: profile with `--profile` → analyze with `analyze-profile` → identify the slowest actions via `--execution_log_json_file` → apply the targeted fix → re-profile to verify the improvement.

Remove or collapse the generic filler sections ("Do not use this skill when", "Limitations") and the Key Concepts table, since they restate Bazel basics Claude already knows and add no actionable value.

Move the seven templates into separate reference files under references/ (e.g., references/templates.md) and either create the referenced resources/implementation-playbook.md or remove the dangling pointer, so SKILL.md becomes a lean overview with clearly signaled one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The templates are dense and information-rich, but the "Key Concepts" table explains basics Claude already knows (Target, Package, Label, Rule), and the "Instructions", "Do not use this skill when", and "Limitations" sections are generic filler ("Apply relevant best practices and validate outcomes"), fitting anchor 3's 'some unnecessary explanation' rather than 2's pervasive padding.	3 / 5
Actionability	Mostly executable, copy-paste-ready guidance: complete .bazelrc and WORKSPACE configs, BUILD files, a custom Starlark rule, and concrete bazel query/profiling commands. Minor gaps — `sha256 = "..."` placeholders in http_archive and the fragile `git diff`-based query — keep it below anchor 5's fully copy-paste-ready bar.	4 / 5
Workflow Clarity	There is no sequenced optimization workflow: the natural profile → analyze → fix → re-measure loop is only implicit in adjacent commands, the Instructions are abstract ("Apply relevant best practices and validate outcomes"), and no validation checkpoints exist anywhere, matching anchor 2's 'rough sequence present but many gaps; validation absent' more than anchor 3's listed steps.	2 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/), yet ~400 lines including seven full templates are inlined in SKILL.md — content that clearly belongs in separate reference files — and the single internal reference, `resources/implementation-playbook.md`, points to a file that does not exist. This matches anchor 2: minimal effective structure despite headers, with a broken sole reference.	2 / 5
	Total	11 / 20 Passed

Description

82%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.

The description is well-constructed: it explicitly answers both what and when, uses natural trigger terms in third person, and occupies a clearly distinct Bazel-specific niche. Its only weakness is that the capability statement is a single high-level action, with specifics deferred to the trigger clause.

Dimension	Reasoning	Score
Specificity	"Optimize Bazel builds for large-scale monorepos" names the domain with a single generic action; concrete actions like "implementing remote execution" appear only in the trigger clause rather than as stated capabilities, matching anchor 3 rather than 4's 'several specific actions'.	3 / 5
Completeness	It clearly states what the skill does ("Optimize Bazel builds for large-scale monorepos") and explicitly answers when with concrete trigger phrases ("Use when configuring Bazel, implementing remote execution, or optimizing build performance"), in third person — a direct match for anchor 5.	5 / 5
Trigger Term Quality	"configuring Bazel", "implementing remote execution", "optimizing build performance", "large-scale monorepos", and "enterprise codebases" give good natural keyword coverage, but common variations like "remote cache", "BUILD files", or "build times" are missing, so it falls short of anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Every trigger is Bazel-specific ("configuring Bazel", "remote execution", "build performance for enterprise codebases"), giving a clear niche with minimal overlap risk against general build-tool or CI skills, matching anchor 5 rather than 4's minor-overlap case.	5 / 5
	Total	17 / 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/agentic-awesome-skills
Path: skills/bazel-build-optimization/SKILL.md
Commit: 7b534bc

Reviewed: 17 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.