CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-review

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

80

Quality

100%

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

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 compact, actionable skill body: a precise output format, named tag taxonomy, concrete examples, an unambiguous end condition, and explicit scope boundaries, all with zero padding.

DimensionReasoningScore

Conciseness

Lean throughout: no explaining what diffs or review are, every line earning its place, with compressed aphorisms like 'The diff's best outcome is getting shorter.' that assume Claude's competence.

5 / 5

Actionability

Gives a concrete output format spec, five precisely defined tags (delete/stdlib/native/yagni/shrink), and five copy-paste-ready example findings that cover the common cases.

5 / 5

Workflow Clarity

As a single-purpose skill, the single action is unambiguous (review diffs, emit one-line findings, end with 'net: -<N> lines possible.' or 'Lean already. Ship.'), with an explicit terminal condition; the simple-skill exception applies and the skill is read-only so the destructive-cap does not bind.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear sections (Format, Examples, Scoring, Boundaries); the simple-skill exception allows a top score on well-organized sections alone.

5 / 5

Total

20

/

20

Passed

Description

100%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 tight, third-person description that crisply states what the skill does, how it formats output, and exactly when to invoke it. It is specific, trigger-rich, and clearly distinct from sibling review skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions and target categories ('reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility') plus the output contract ('One line per finding: location, what to cut, what replaces it'), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (finds deletable over-engineering with a one-line finding format) and when (a dedicated 'Use when...' clause listing concrete trigger phrases and the slash command).

5 / 5

Trigger Term Quality

Provides several natural trigger phrases users would say ('review for over-engineering', 'what can we delete', 'is this over-engineered', 'simplify review') plus the /ponytail-review invocation, covering synonyms and the slash command.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche scoped to over-engineering only and explicitly distinguishes itself from correctness review ('Complements correctness-focused review, this one only hunts complexity'), minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.