CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

perf-loop

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

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/perf-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exemplar of token efficiency — dense, non-obvious guidance with zero padding — and the 8-step loop is clearly sequenced with real validation gates (benchmark sanity proof, correctness checks, reproducibility). The main weakness is actionability: several steps direct Claude to perform measurements (profiling, host-load recording, statistical baselining) without naming tools or commands, leaving key execution details to be invented. Naming the specific profiler and load-recording commands would make the loop fully executable.

Suggestions

Name the concrete tooling for measurement steps, e.g. which profiler to use for the hot path and which command records host load (uptime / /proc/loadavg / perf stat).

Quantify "statistically useful baseline" — e.g. a minimum round count or the interleaved-pair sample size needed before comparing.

Add one explicit recovery line after step 6, e.g. "If the candidate is not reproducible, revert it and return to step 4," to close the feedback loop.

DimensionReasoningScore

Conciseness

The 25-line body is lean and assumes competence: every line carries non-obvious, project-specific guidance such as "Under load, compare CPU time, not wall time" and "Other work on the host can change one run by more than the gain". No token is spent explaining concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Some steps are concretely executable ("Run the base binary and the candidate as interleaved pairs (base, candidate, base, and so on)", "Run `review`"), but key details are missing: no profiler is named for "Profile the hot path", no command for "record the host load", and no definition of a "statistically useful baseline". This matches 'some concrete guidance but incomplete; missing key details' rather than 4, which requires mostly executable commands with only minor gaps.

3 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with explicit checkpoints: prove the benchmark can see the problem (step 1), minimum rounds and target (step 2), re-run with correctness checks (step 5), and the keep-only-if-reproducible gate (step 6). It falls short of 5 because error recovery is implicit — there is no explicit instruction to discard a failed candidate and loop back to step 4.

4 / 5

Progressive Disclosure

This is a sub-50-line, single-purpose skill with no bundle files (references/, scripts/, assets/ do not exist) and no external references needed; the single well-ordered numbered list is fully appropriate structure. Per the rubric's simple-skill guidance, this earns the top anchor.

5 / 5

Total

17

/

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 is concise, third-person, and specific about the method (stable benchmarks, before-and-after evidence, correctness gates), but it omits any 'Use when...' trigger guidance and lacks natural synonym keywords like 'faster' or 'speed up'. This caps completeness and trigger-term quality at the midpoint. Adding an explicit when-clause with natural user phrasings would lift the two heaviest-weighted dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when asked to speed up Fallow, reduce latency, or when Fallow benchmarks regress."

Include natural synonyms users would actually say — "faster", "speed up", "slow", "profiling" — alongside "optimize performance".

Optionally note the scope boundary (e.g., that this covers code-level optimization, not infra scaling) to reduce overlap with generic performance skills.

DimensionReasoningScore

Specificity

"Iteratively optimize Fallow performance with stable benchmarks, before-and-after evidence, and correctness gates" names the domain plus several concrete method elements (stable benchmarks, before-and-after evidence, correctness gates), matching the 'lists several specific actions; minor gaps' anchor. It falls short of 5 because coverage is not comprehensive (e.g., no mention of profiling, targets, or regression comparison), and above 3 because it goes beyond domain plus 1-2 actions.

4 / 5

Completeness

The 'what' is clear (iteratively optimize Fallow performance via benchmarks, evidence, and gates), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is entirely absent rather than merely imprecise, and not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like "optimize", "performance", and "benchmarks" are present, but common variations users would naturally say — "faster", "speed up", "slow", "profiling", "latency" — are missing, matching the 'some relevant keywords but missing common variations or synonyms' anchor. It is above 2 because the terms are domain-relevant rather than generic, and below 4 because synonym coverage is thin.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to the named project "Fallow" with method-specific terms (correctness gates, before-and-after evidence) gives it a mostly distinct niche with only minor overlap risk against generic performance-tuning skills. It is not 5 because without an explicit trigger clause a generic 'optimize performance' request could still match a competing skill.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.