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.

76

Quality

95%

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-audit in DietrichGebert/ponytail

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, well-structured audit spec with a concrete tag taxonomy and an exact output format, assuming Claude's competence throughout. The only slight gap is that the workflow is implied by section order rather than given as an explicit sequenced process with checkpoints.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept explanations Claude already knows; reuses ponytail-review conventions by reference ("Same as ponytail-review") so every token earns its place.

5 / 5

Actionability

Gives a concrete tag taxonomy with per-tag replacement guidance, explicit hunt targets, and an exact output format ("`<tag> <what to cut>. <replacement>. [path]`" plus the "`net: -<N> lines, -<M> deps possible.`" closer) — fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

The single audit-then-report action is unambiguous with a clear output contract, but the workflow is conveyed via topical sections (Tags, Hunt, Output, Boundaries) rather than an explicit sequenced/checkpointed process, leaving minor gaps.

4 / 5

Progressive Disclosure

Under 50 lines with no external file references needed, and well-organized into clearly labeled sections; per the simple-skill exception this earns a 5 on organization alone.

5 / 5

Total

19

/

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.

The description is concise, concrete, and fully answers both what the skill does and when to use it, with strong natural trigger phrases. Its only weakness is minor overlap risk with the closely related ponytail-review skill, which it distinguishes by scope rather than by fully disjoint triggers.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "delete, simplify, or replace with stdlib/native equivalents" — giving comprehensive coverage of what the audit produces, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both what ("Whole-repo audit for over-engineering... a ranked list of what to delete, simplify, or replace") and when ("Use when the user says...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists natural phrases users would actually say ("audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat") plus the skill name and slash form, matching comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (repo-wide over-engineering audit) with distinct triggers, but explicitly compares to and overlaps the sibling ponytail-review skill, leaving minor conflict risk between the two.

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