CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ponytail-gain

Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the agentic benchmark averages. One-shot display.

64

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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, high-quality one-shot display skill: it hands Claude the exact artifact to render, states where the figures come from, and polices an honesty boundary against fabricating per-repo savings. Its only blemish is a slight repetition of the one-shot constraint between the opening and the Boundaries section.

DimensionReasoningScore

Conciseness

The body is lean — provenance, an exact ASCII template, and an honesty boundary with no filler. The only trimmable redundancy is that the closing 'One-shot display. Edits nothing, changes no mode' restates the opening 'One-shot: do NOT change mode, write flag files, or persist anything'.

4 / 5

Actionability

The full ASCII scoreboard is given verbatim with figures, bar semantics ('bar length shows ponytail as a share of the no-skill baseline; the label carries the exact figure'), and pointer lines, making the single action copy-paste ready.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action ('Display this scoreboard when invoked') is unambiguous, with explicit negative constraints (no mode change, no persistence, never invent per-repo numbers); no destructive or batch operations apply.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed; content is organized into clear sections (Scoreboard, Honesty boundary, Boundaries) and pointers to /ponytail-debt and /ponytail-audit are clearly signaled rather than buried.

5 / 5

Total

19

/

20

Passed

Description

62%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 specific, distinctive description that clearly states what the skill renders, anchored by a unique niche name. Its weaknesses are the absence of any 'Use when...' trigger guidance and thin coverage of the natural phrases a user would actually type.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for ponytail gains, the benchmark scoreboard, or how much ponytail saves.'

Include natural keyword variations users might say — 'gains', 'savings', 'benchmark results', 'scoreboard' — alongside the proper noun 'ponytail'.

State the invocation mode in trigger terms (e.g. 'when asked to show or display the ponytail results') so 'when to use' is explicit, not just the 'what'.

DimensionReasoningScore

Specificity

'Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the agentic benchmark averages. One-shot display' names a concrete display action and the specific metrics shown. It stops short of 5 because it covers one action (render a scoreboard) rather than multiple comprehensive capabilities.

4 / 5

Completeness

The 'what' is clear (display a scoreboard of measured impact figures), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ('ponytail', 'scoreboard', 'measured impact', 'agentic benchmark averages') but natural user phrasings and their variations are missing — a user might say 'show the ponytail gains', 'benchmark results', or 'savings numbers'. Fits the anchor 'Some relevant keywords but missing common variations or synonyms' better than 4.

3 / 5

Distinctiveness Conflict Risk

The niche 'ponytail' proper noun plus the scoreboard framing make it essentially impossible to trigger for the wrong skill; clear niche with distinct triggers.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

DietrichGebert/ponytail

Path

.openclaw/skills/ponytail-gain/SKILL.md

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.