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.34x

Quality

—

Does it follow best practices?

Impact

94%

1.34x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

Actionable and well-stocked with executable Bazel templates, but the skill is a long monolithic file with no reference files and lacks sequenced workflows with validation checkpoints for risky operations.

Suggestions

Split large templates and the .bazelrc reference into separate files under references/ (e.g. TEMPLATES.md, BAZELRC.md) and link to them from a concise overview to improve progressive disclosure and conciseness.

Add an explicit sequenced workflow with validation checkpoints for the riskier operations — e.g. remote-execution migration and the custom Docker rule — including build/validate/retry steps.

Trim the inline .bazelrc to the essential settings and move optional remote-cache/remote-exec/platform blocks into a referenced config file to reduce token load.

Dimension	Reasoning	Score
Conciseness	Mostly efficient — no padded concept explanations and largely executable code — but ~380 lines with seven full templates and a large .bazelrc all inline could be tightened or moved to reference files, matching 'mostly efficient but could be tightened' rather than lean.	2 / 3
Actionability	Provides many concrete, copy-paste-ready templates and commands (WORKSPACE, .bazelrc, BUILD files, custom .bzl rule, bazel query recipes, RBE platform setup), matching the anchor for fully executable code and specific examples.	3 / 3
Workflow Clarity	Content is organized into procedural recipes (profiling, query, RBE) but there is no unified sequenced workflow, and risky/batch operations like the custom Docker rule and remote-execution migration lack explicit validation checkpoints, capping it at 2.	2 / 3
Progressive Disclosure	A single monolithic SKILL.md with no reference files; content that could be split (full templates, command reference) is inline. It is well-sectioned so it rises above a wall of text, but with no one-level-deep references it cannot reach 3.	2 / 3
	Total	9 / 12 Passed

Description

100%

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: third-person voice, concrete capabilities, explicit 'Use when' triggers, and a distinct niche. It clearly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Optimize Bazel builds', 'configuring Bazel', 'implementing remote execution', 'optimizing build performance' — matching the anchor for several specific concrete actions rather than a vague or partial list.	3 / 3
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'), matching the anchor requiring explicit triggers for both.	3 / 3
Trigger Term Quality	Natural terms a user would say ('Bazel', 'remote execution', 'build performance', 'monorepos', 'enterprise codebases') give good coverage, matching the top anchor; not reduced to 2 since the term set is broad and natural.	3 / 3
Distinctiveness Conflict Risk	A clear niche — Bazel build optimization for large-scale monorepos — with distinct triggers unlikely to overlap with other skills, matching the top distinctiveness anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Commit: abece4a

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