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

72%

Does it follow best practices?

Impact

97%

1.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/bazel-build-optimization/SKILL.md

The canonical home for this skill is bazel-build-optimization in sickn33/agentic-awesome-skills

Quality

Content

57%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 rich with concrete, executable Bazel templates but is held back by generic fluff in the Instructions, a Key Concepts table restating basics Claude already knows, missing validation checkpoints in workflows, and a monolithic structure with a dangling reference to a non-existent playbook file.

Suggestions

Remove the generic Instructions section ("Clarify goals... validate outcomes") and the Key Concepts table, or replace them with Bazel-specific guidance Claude would not already know.

Add explicit validation checkpoints to the remote-execution and profiling workflows (e.g., verify the cache hit rate after configuring remote-cache, re-run analyze-profile after changes).

Move the bulkier templates (WORKSPACE, .bazelrc, custom rule) into files under references/ and point to them with clearly signaled one-level-deep links; create the referenced resources/implementation-playbook.md or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code templates, but the generic Instructions section ("Clarify goals... Apply relevant best practices and validate outcomes") is fluff and the Key Concepts table explains basic Bazel concepts (Target, Package, Label, Rule) Claude already knows, so it sits at anchor 3 rather than 4.	3 / 5
Actionability	Seven concrete, mostly copy-paste-ready templates (WORKSPACE, .bazelrc, BUILD files, custom rule, query commands, platform/toolchain, profiling) cover common cases, but placeholders like `sha256 = "..."` keep it from being fully executable as-is, matching anchor 4.	4 / 5
Workflow Clarity	The Instructions section offers only a vague abstract sequence ("Clarify goals... validate outcomes") with no concrete checkpoints, and the multi-step procedures (remote execution, profiling) lack explicit validate-fix-retry loops, matching anchor 3.	3 / 5
Progressive Disclosure	Section headers provide reasonable structure, but all seven full templates are inlined in a single monolithic file and the sole reference (`resources/implementation-playbook.md`) points to a path with no matching bundle file present, matching anchor 3.	3 / 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.

The description is strong: it concisely states both what the skill does and when to use it, with concrete Bazel-specific trigger phrases. Minor specificity gaps (no mention of custom rules, debugging, or migration) keep it just below a perfect specificity score.

Dimension	Reasoning	Score
Specificity	Names the domain ("Bazel builds", "large-scale monorepos") and several concrete actions ("configuring Bazel", "implementing remote execution", "optimizing build performance"), but the actions are somewhat high-level and omit coverage the body provides (custom rules, debugging, migration), so it sits at anchor 4 rather than 5.	4 / 5
Completeness	It clearly states what ("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"), matching anchor 5.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ("Bazel", "remote execution", "build performance", "monorepos"), but a few common variations like "build times" or "remote cache" are missing, matching anchor 4.	4 / 5
Distinctiveness Conflict Risk	Bazel build optimization for large monorepos is a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/bazel-build-optimization/SKILL.md
Commit: 57c135b

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