perf-loop

Iteratively optimize Fallow performance with stable benchmarks, before-and-after evidence, and correctness gates.

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/perf-loop/SKILL.md

Quality

Content

85%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 a concise, well-sequenced performance loop with strong validation checkpoints, scoring high on conciseness, workflow clarity, and structure. Its only weak spot is actionability: the steps name what to do but not the specific tools or commands to execute.

Suggestions

Add one or two concrete executable cues, e.g. a profiler command (perf/flamegraph) and how to invoke the stable benchmark.

Specify what 'Run review' means or link the exact command/step, so the final action is unambiguous.

Optionally name the correctness-gate command(s) so 'correctness checks' is copy-paste ready rather than implied.

Dimension	Reasoning	Score
Conciseness	Lean ~18-line body with no padded concept explanation; every line earns its place and assumes Claude's competence.	5 / 5
Actionability	Steps are concrete directives with a validation gate, but no executable commands, profiler invocations, or benchmark tooling are named, leaving guidance high-level rather than copy-paste ready.	3 / 5
Workflow Clarity	A clearly numbered sequence with explicit validation checkpoints (re-run the same benchmark, keep the change only when reproducible with no contract regression) and a guardrail closing line.	5 / 5
Progressive Disclosure	A short, single-purpose skill under 50 lines with no external references needed; the simple-skill exception applies and the content is well-organized.	5 / 5
	Total	18 / 20 Passed

Description

58%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 conveys a clear, specific purpose tied to a distinct niche but omits any explicit 'when to use' trigger clause, capping its completeness. Adding a 'Use when...' clause with natural user phrases would lift the weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to speed up or optimize Fallow, or reports slow performance.'

Include natural synonyms a user would actually say, such as 'speed up', 'make it faster', or 'slow', alongside 'optimize performance'.

Keep the third-person voice but make the 'when' as concrete as the 'what' to push completeness and trigger quality to 4–5.

Dimension	Reasoning	Score
Specificity	Names the domain ('optimize Fallow performance') and several concrete methods ('stable benchmarks', 'before-and-after evidence', 'correctness gates'), with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Relevant terms like 'performance', 'optimize', and 'benchmarks' appear, but common natural variations a user would say ('speed up', 'make it faster', 'slow') are missing.	3 / 5
Distinctiveness Conflict Risk	Tied to the specific 'Fallow' project with a performance/benchmark niche, making it mostly distinct with only minor overlap risk against general profiling skills.	4 / 5
	Total	14 / 20 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/perf-loop/SKILL.md
Commit: 7e1e075

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