CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-debt

Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.

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

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.

The body is a tight, fully-executable recipe: one grep command, one output template, one flagging rule, and one summary format, organized into clear sections with explicit read-only boundaries. It assumes Claude's competence and wastes no tokens on background explanation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's intelligence — no explanation of what grep or git blame is — and every line earns its place; it states the convention and gives the command rather than padding.

5 / 5

Actionability

Fully executable guidance is given: the exact grep command, the exact output row template, an optional `git blame -L<line>,<line>` command, the `no-trigger` tagging rule, and the exact end-summary format ('<N> markers, <M> with no trigger.' / 'No ponytail: debt. Clean ledger.').

5 / 5

Workflow Clarity

The skill is single-purpose and read-only (no destructive or batch mutation), so the simple-skill exception applies; the sequence Scan → Output → Boundaries is unambiguous with the scan, formatting, flagging, and summary steps clearly laid out.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Scan, Output, Boundaries) and no need for external references; the simple-skill rule allows a 5 for well-organized content with no bundle files.

5 / 5

Total

20

/

20

Passed

Description

90%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 concrete, trigger-rich, and fully answers both what the skill does and when to invoke it, with a distinct niche that minimizes conflict risk. Its only minor gap is that the underlying task is single-purpose, so the breadth of specific actions is naturally modest.

DimensionReasoningScore

Specificity

Concrete actions are named — 'Harvest every `ponytail:` comment in the codebase into a debt ledger' and flagging rows with 'no-trigger' — giving several specific actions rather than a single one, but the domain is a single-task skill so coverage is good rather than exhaustive.

4 / 5

Completeness

It explicitly answers both 'what' (harvest `ponytail:` comments into a debt ledger, one-shot, changes nothing) and 'when' with concrete trigger phrases ('Use when the user says...'), matching the score-5 anchor.

5 / 5

Trigger Term Quality

Six natural trigger phrases a user would actually say are listed ('ponytail debt', '/ponytail-debt', 'what did ponytail defer', 'list the shortcuts', 'ponytail ledger', 'what did we mark to do later'), giving comprehensive coverage of natural terms.

5 / 5

Distinctiveness Conflict Risk

A narrow niche built around the `ponytail:` comment marker with distinct trigger phrases and an explicit 'changes nothing' boundary, giving minimal conflict risk with other skills.

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