CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-gain

Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".

80

Quality

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.

A tight, well-structured single-purpose skill that gives Claude the exact artifact to render plus a clear honesty boundary and reversion behavior. It adds only what Claude would not already infer and is appropriately scoped for a one-shot display.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining what a benchmark or median is; every line earns its place, with only minor redundancy in the 'Boundaries' section restating the one-shot rule.

3 / 3

Actionability

Provides a verbatim, copy-paste-ready ASCII scoreboard template with exact figures and an explicit rendering rule ('Render plain ASCII bars. The bar length shows the measured range; the label carries the exact figure'), which is concrete executable output for a display skill.

3 / 3

Workflow Clarity

A single-purpose display skill with an unambiguous action ('Display this scoreboard when invoked') and a clear revert path ('stop ponytail'); per the simple-skill note, an unambiguous single action scores 3 without needing validation checkpoints.

3 / 3

Progressive Disclosure

Under 50 lines with no external bundle files needed and well-organized sections (Scoreboard, Honesty boundary, Boundaries), satisfying the simple-skill allowance for a top score on organization alone.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person description that clearly states what the skill does, when to use it via explicit triggers, and how it differs from related skills. It avoids fluff and over-claims while remaining specific.

DimensionReasoningScore

Specificity

Enumerates concrete actions and measurable axes ('less code, less cost, more speed, from the benchmark medians') tied to a specific artifact (a compact scoreboard), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (show measured impact as a scoreboard) and when (explicit 'Trigger:' clause), so it is not capped at 2 for a missing trigger clause.

3 / 3

Trigger Term Quality

Provides good coverage of natural user phrases plus the slash command ('/ponytail-gain', 'ponytail gain', 'what does ponytail save', 'show ponytail impact', 'ponytail scoreboard'), matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The 'ponytail' namespace and distinct triggers give it a clear niche, and it explicitly distinguishes itself ('not a persistent mode, and not a per-repo number'), making conflict unlikely.

3 / 3

Total

12

/

12

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.