CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ponytail-debt

List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.

74

Quality

93%

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

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

An exemplary one-shot reporting skill: fully executable command, exact output format, explicit edge-case and false-positive handling, and a tightly bounded read-only scope. Nothing is padded and nothing essential is missing for the task it describes.

DimensionReasoningScore

Conciseness

The ~37-line body is lean: every clause drives execution (grep pattern, filtering rule, row format, edge cases) and nothing explains concepts Claude already knows. Each sentence earns its tokens, matching the "lean and efficient" anchor.

5 / 5

Actionability

The skill gives a copy-paste-ready command (`git grep --no-index --exclude-standard -nE '(#|//|/[*]) ?(shortcut|ponytail):'`), an exact row template with the convention to parse, an optional `git blame -L<line>,<line>` extension, and concrete outputs for both the found and empty cases.

5 / 5

Workflow Clarity

The single task is unambiguously sequenced: scan with the grep, skip non-deferral hits, emit one row per marker grouped by file, tag no-trigger markers, and end with a mandated summary line plus the "No shortcut debt. Clean ledger." empty case. It is read-only, so the destructive/batch validation cap does not apply, and the false-positive filter and empty-case handling serve as its checkpoints.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external reference files; the body is organized into three clearly labeled sections (Scan, Output, Boundaries) and no bundle files exist, so the simple-skill guideline for a 5 applies.

5 / 5

Total

20

/

20

Passed

Description

83%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 description in third-person voice that states concrete actions and pairs them with an explicit, multi-phrase trigger clause. The only gaps are near-synonym triggers and a slightly underspecified picture of the ledger's row contents.

DimensionReasoningScore

Specificity

"List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing." names several concrete actions (enumerate marker comments, produce a ledger, read-only one-shot report), but omits what each ledger row contains (ceiling, upgrade path, no-trigger flag), leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both questions: the what is "List every `shortcut:` comment ... as a debt ledger. One-shot report, changes nothing." and the when is a concrete "Use for" clause with multiple trigger phrases. Not 4 because the when-guidance is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

"Use for 'ponytail debt', 'what did ponytail defer', 'list the shortcuts', /ponytail-debt" covers multiple natural phrases plus the slash command, but misses close variants users might say such as "shortcut debt" or "deferred work".

4 / 5

Distinctiveness Conflict Risk

The ponytail-debt niche with its own marker vocabulary and /ponytail-debt trigger is clearly distinct, but "list the shortcuts" could plausibly match a keyboard-shortcut listing skill, so minor overlap risk remains. Not 5 because of that collision; not 3 because the core triggers ("ponytail debt", "what did ponytail defer") are unambiguous.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

DietrichGebert/ponytail

Path

skills/ponytail-debt/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.