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

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.

A lean, dense, fully actionable review skill that defines an exact output format with concrete examples and clear termination criteria. It assumes Claude's intelligence, stays within its niche, and is well-organized for a simple single-purpose skill.

DimensionReasoningScore

Conciseness

Roughly 45 lines with no concept over-explanation; it assumes Claude's competence, defining only the output format and tag semantics, and every section earns its place.

5 / 5

Actionability

Gives a concrete output spec ('L<line>: <tag> <what>. <replacement>.'), five precisely defined tags, and several copy-ready ✅ examples covering the common cases; Claude knows exactly what to produce.

5 / 5

Workflow Clarity

Single-purpose, unambiguous action (review diff, emit tagged one-liners, terminate with 'net: -<N> lines possible' or 'Lean already. Ship.'); the destructive-cap does not apply since it explicitly lists rather than applies fixes.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clearly labeled sections (Format, Examples, Scoring, Boundaries); no bundle files exist to evaluate, and none are needed.

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 highly specific, well-triggered description that clearly states a focused niche (over-engineering deletion review) and gives multiple natural activation phrases. It distinguishes itself from correctness-focused review and uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete deletion categories ('reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility') plus the one-line finding format with location/cut/replacement, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (finds deletable over-engineering, one line per finding) and 'when' (an explicit 'Use when the user says...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Provides natural user phrases ('review for over-engineering', 'what can we delete', 'is this over-engineered', 'simplify review') plus the /ponytail-review invocation, covering synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

'focused exclusively on over-engineering' and 'Complements correctness-focused review, this one only hunts complexity' carve a clear niche with minimal overlap risk against general review skills.

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
marmelab/atomic-crm
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.