CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-performance

Use when reviewing a branch diff for performance defects — redundant database round trips, N+1 queries, unbounded reads, per-request layer rebuilds, wasted client fetches, and build steps that ship a broken artefact — and reporting findings with P-C/W/I IDs in the four-field format.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 exceptionally actionable, well-sequenced review procedure with executable commands, explicit validation checkpoints, and recovery instructions for the failure modes it guards against. Its weaknesses are repetition — the report-shape rules are restated three times where a single statement plus cross-references would do — and a miscounted reference ("Eight" sections vs the ten actually listed and shipped).

Suggestions

Correct the count in 'The rest of the checklist': it says "Eight more sections live in references/checklists.md" but names ten, and references/checklists.md contains exactly ten sections.

State the heading-placement rules (summary sentence → Performance findings, counted number → Measurements, environment caveat → Sections checked) once in Step 0 and have the Step 2 mid-run check and the final check reference them, instead of re-explaining them three times.

Trim duplicated enforcement prose such as the repeated 'never rewritten / read it back first' warnings and restatements like "Routing widens attention; it never narrows it. A grep hit is a reason to open a section, never a reason to stop reading." to reduce the body's token cost.

DimensionReasoningScore

Conciseness

The four-heading placement rules are explained three separate times — Step 0 ("a summary sentence goes at the top of `## Performance findings`, a number you counted goes in `## Measurements`, an environment caveat goes at the end of `## Sections checked`"), again mid-run in Step 2's shape check, and again in "Check the file before you finish" ("a summary sentence belongs at the top of `## Performance findings`, a number you counted in `## Measurements`, an environment caveat at the end of `## Sections checked`"). Mostly efficient otherwise — no padding with concepts Claude already knows — but the triplicated rules and rhetorical restatements ("Routing widens attention; it never narrows it") go beyond the 'minor instances' of the 4 anchor.

3 / 5

Actionability

Every step is copy-paste executable: the heredoc that writes the report skeleton, the base-branch resolution block (`BASE=$(git config --get branch.$(git branch --show-current).gh-merge-base || echo main)`), the grep routing table with literal patterns, the `grep -c '^## …'` shape checks with expected output ("It must print `4`"), and `grep -rn '<gateName>(' <workspace>/src/routes` for counting callers. Not 4: nothing is left as pseudocode or high-level hint.

5 / 5

Workflow Clarity

The process is explicitly sequenced (Step 0 skeleton → Step 1 route → Step 2 work sections → report shape → final check) with validation checkpoints and error-recovery loops at both mid-run ("If it prints less … restore the 4 headings, put the finding back under the right one, and edit from then on") and completion (both grep counts "must print `4`"). This matches the 5 anchor's explicit validation with feedback loops.

5 / 5

Progressive Disclosure

The split is appropriate and well signaled — "Eight more sections live in `references/checklists.md` … open the file whenever Step 1 routes to one of them" — and the referenced file is real and one level deep (verified: it exists and contains the routed checklist sections). But the text says "Eight more sections" while naming ten (Loops and batching, Indexes, Unbounded reads, Effect runtime, Client fetches, SolidJS reactivity, Bundle and loading, Layout and event handlers, Build and deploy, Changesets — ten in the reference file too), and the main body still inlines two full checklist sections, leaving a minor organization gap per the 4 anchor rather than the clean 5.

4 / 5

Total

17

/

20

Passed

Description

92%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.

A strong description: it opens with an explicit 'Use when' trigger, names the target artifact (branch diff), enumerates the specific defect classes it hunts, and pins down the report format. The only gap is missing common synonyms (slow, latency, optimize) that a user might naturally say when asking for a performance pass.

DimensionReasoningScore

Specificity

The description enumerates concrete, specific defect classes — "redundant database round trips, N+1 queries, unbounded reads, per-request layer rebuilds, wasted client fetches, and build steps that ship a broken artefact" — plus a concrete reporting action ("reporting findings with P-C/W/I IDs in the four-field format"), matching the comprehensive multi-action anchor rather than the 'minor gaps' anchor at 4.

5 / 5

Completeness

Both halves are explicit: what — "reviewing a branch diff for performance defects — … — and reporting findings with P-C/W/I IDs in the four-field format" — and when — the leading "Use when reviewing a branch diff for performance defects" names the concrete triggering situation. Not 4, because the 'when' is explicit and concrete rather than something that 'could be more specific'.

5 / 5

Trigger Term Quality

Natural developer phrasings are present — "reviewing a branch diff", "performance defects", "N+1 queries", "database round trips", "unbounded reads" — giving good keyword coverage, but common synonyms a user might say ("slow", "latency", "optimize", "perf review") are absent, so it falls short of the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — performance-only review of a branch diff — with a distinctive output contract ("P-C/W/I IDs in the four-field format") that no neighboring skill (general code review, PR prep) shares, so conflict risk is minimal per the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/review-performance/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.