CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-review

Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.

71

Quality

87%

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

The canonical home for this skill is ponytail-review in DietrichGebert/ponytail

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally tight, single-purpose instruction skill: concrete format, per-tag examples, an explicit stop condition, and well-organized sections with no unnecessary tokens. It fully leverages the simple-skill exceptions for workflow clarity and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("One line per finding: location, what to cut, what replaces it"), with every line earning its place and no padding or restated concepts.

5 / 5

Actionability

Concrete output format (`L<line>: <tag> <what>. <replacement>.`), a defined tag set with one concrete example each, and a precise end metric (`net: -<N> lines possible.`) make the guidance fully executable; code absence is not penalized for an instruction-only skill.

5 / 5

Workflow Clarity

The single action (emit one-line findings, then the net metric or "Lean already. Ship." stop condition) is unambiguous; the skill is analysis-only so the destructive/batch validation cap does not apply, and the simple-skill exception yields 5.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the body is organized into clear sections (Format, Examples, Scoring, Boundaries), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

75%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 sharp, distinctive description that names concrete finding categories and a clear output format. It falls short of full completeness only because it omits an explicit "Use when..." trigger clause, which the rubric caps at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing a diff that may be over-engineered or when the user wants to simplify/cut code."

Broaden natural trigger terms to include synonyms like "simplify", "too complex", or "YAGNI" to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete finding categories ("reinvented stdlib, needless deps, speculative abstractions") plus a concrete output format ("One line per finding"), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

The "what" is clear (review a diff for over-engineering, find what to delete) but there is no explicit "Use when..." trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"over-engineering" and "what to delete" are natural user phrases, but common synonyms like "simplify", "too complex", or "YAGNI" are absent, leaving minor gaps in keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The over-engineering/deletion niche with specific category triggers is clearly distinct from general review skills, with minimal conflict risk.

5 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
DietrichGebert/ponytail
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.