CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-audit

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.

74

Quality

91%

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

86%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 tight, well-structured instruction skill that assumes Claude's competence and stays in scope. Adding one worked example finding and a brief numbered sequence would round out actionability and workflow clarity.

Suggestions

Add one or two fully worked example finding lines (e.g. `yagni: AbstractFactory with one product. Inline the call. [src/factory.ts]`) to make the output format copy-paste concrete.

Express the Hunt -> rank -> Output flow as a short numbered sequence so the workflow is explicit rather than implied by section order.

Optionally show the 'net:' tally line with a concrete example to anchor the output contract.

DimensionReasoningScore

Conciseness

Lean and efficient (~30 lines) with no over-explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides a concrete output template and per-tag replacement guidance, but lacks a fully worked example finding line covering a common case.

4 / 5

Workflow Clarity

Hunt-to-Output sequence with an explicit ranking rule is clear; the skill is single-purpose and read-only, so no validation checkpoint is required, but numbered steps are absent.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, organized into well-signaled sections (Tags/Hunt/Output/Boundaries); the simple-skill exception applies.

5 / 5

Total

18

/

20

Passed

Description

96%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, concise description that names concrete actions, comprehensive natural triggers, and explicit use-when guidance in third person. The only weakness is mild overlap risk with the closely-named ponytail-review sibling.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'what to delete, simplify, or replace with stdlib/native equivalents' — with comprehensive coverage of the audit's outputs.

5 / 5

Completeness

Explicitly answers both 'what' (whole-repo over-engineering audit producing a ranked cut list) and 'when' via a concrete 'Use when...' clause with named trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural triggers including synonyms and the slash form: 'audit this codebase', 'find bloat', 'what can I delete from this repo', 'ponytail-audit', '/ponytail-audit'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (over-engineering, repo-wide) with distinct triggers, but the sibling 'ponytail-review' naming creates minor overlap risk, keeping it just below a 5.

4 / 5

Total

19

/

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.