binary-loop

Iteratively reduce Fallow binary size using cargo-bloat and release-build measurements while preserving features, performance, and compatibility.

Quality

71%

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 ./.agents/skills/binary-loop/SKILL.md

Quality

Content

85%

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

The body is a tight, well-sequenced iterative loop with an explicit validation checkpoint and no wasted tokens. Its main weakness is actionability: it names tools but rarely provides the concrete commands to run them.

Suggestions

Add the exact measurement command, e.g. `cargo bloat --release --crates`, so step 1 is copy-paste ready.

Specify the rebuild command and the verification command referenced in steps 4 and 5.

Clarify what 'verification passes' means in step 5 (e.g. which tests or CI command must pass).

Dimension	Reasoning	Score
Conciseness	Seven lean numbered steps plus one constraint line, with no concept explanations Claude already knows and no padding; every token earns its place.	3 / 3
Actionability	Names tools (cargo-bloat, `review`) but gives no concrete commands for measuring or rebuilding, and 'Implement a bounded change' is abstract; guidance is actionable in outline but missing executable specifics.	2 / 3
Workflow Clarity	Steps are explicitly numbered with a keep/discard validation gate (step 5: 'only when size improves and verification passes') and a repeat loop (step 6), giving a clear feedback loop for this iterative batch operation.	3 / 3
Progressive Disclosure	A simple, single-purpose skill under 50 lines with no bundle files present and well-organized sections, which the rubric allows to score 3 without external file references.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 specific and clearly distinguishable but lacks an explicit 'when to use' trigger clause and broader natural keyword coverage. It answers 'what' well but leaves 'when' only implied.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill, e.g. when the user asks to reduce or shrink the Fallow binary.

Broaden trigger terms to include user-natural variations like 'shrink the binary', 'strip unnecessary code', or 'optimize release size'.

Enumerate concrete actions (e.g. measure, profile, trim, rebuild) to lift specificity toward multiple listed actions.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('Fallow binary size') and tooling ('cargo-bloat and release-build measurements') but describes a single action rather than listing multiple distinct concrete actions like the score-3 anchor.	2 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric this caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user might say ('binary size', 'cargo-bloat', 'release-build') but omits common variations users would actually voice like 'shrink', 'strip', or 'optimize the binary'.	2 / 3
Distinctiveness Conflict Risk	The Fallow-specific scope plus cargo-bloat tooling carve out a clear niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 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: fallow-rs/fallow
Path: .agents/skills/binary-loop/SKILL.md
Commit: 55944e8

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