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.

68

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an exceptionally well-crafted skill. It's maximally concise while being fully actionable—the tag taxonomy, format specification, and concrete examples give Claude everything needed to perform the task. The boundaries section smartly scopes the skill and the escape hatch ('stop ponytail-review') shows thoughtful design. The contrast between the ❌ and ✅ examples is particularly effective.

DimensionReasoningScore

Conciseness

Extremely lean. Every line earns its place—no explanations of what over-engineering is, no preamble about code review philosophy. Tags are terse keyword definitions. Examples are compact and illustrative.

3 / 3

Actionability

The format specification is precise and copy-paste ready. Five concrete good examples with exact output format, plus a bad example showing what to avoid. The scoring line and boundary conditions are specific and unambiguous.

3 / 3

Workflow Clarity

This is a single-task skill (review a diff, output findings) with a clear sequence: apply tags per finding, end with net line count, handle the clean-diff case. The boundaries section clearly scopes what's in and out. No destructive operations requiring validation checkpoints.

3 / 3

Progressive Disclosure

For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Format, Examples, Scoring, Boundaries). No monolithic walls of text, no unnecessary splitting needed.

3 / 3

Total

12

/

12

Passed

Description

67%

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 and specific about what it does, with a clear niche that distinguishes it from general code review skills. Its main weakness is the lack of an explicit 'Use when...' clause and some missing natural trigger terms that users might employ when requesting this kind of review.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to review code for over-engineering, unnecessary complexity, or wants to simplify a codebase.'

Include additional natural trigger terms like 'code review', 'simplify', 'YAGNI', 'unnecessary complexity', 'refactor', or 'too complex'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: reviewing diffs, finding reinvented stdlib, needless dependencies, speculative abstractions, and specifies output format (one line per finding).

3 / 3

Completeness

Clearly answers 'what' (review diffs for over-engineering, find things to delete) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes some natural terms like 'diff', 'over-engineering', 'deps', 'abstractions', but misses common user phrases like 'code review', 'simplify', 'refactor', 'complexity', or 'YAGNI'. Users might not naturally say 'speculative abstractions'.

2 / 3

Distinctiveness Conflict Risk

Has a clear niche: over-engineering detection in diffs. The specific focus on deletion candidates (reinvented stdlib, needless deps, speculative abstractions) distinguishes it well from general code review or linting skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.