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

94%

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

A compact, highly actionable read-only report skill with executable commands, a precise output schema, edge-case handling, and clean section structure. The only soft spot is the absence of an explicit validation checkpoint, which is largely unnecessary for a non-destructive one-shot report.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explaining of what grep, git blame, or debt ledgers are — with every line carrying actionable content; matches the 'lean and efficient' anchor.

5 / 5

Actionability

Provides a copy-paste grep command, a concrete per-row output template, a `git blame` add-on, the no-trigger rot tag, the closing summary format, and the empty-result fallback — fully executable coverage of the common cases.

5 / 5

Workflow Clarity

Clear Scan → Output → Boundaries sequence with a built-in rot-risk check (no-trigger tag) and handled empty case; sits just below 5 because there is no explicit validation/checklist step, though as a read-only report it does not require destructive-operation feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present; the Scan/Output/Boundaries sections are well-organized, satisfying the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

95%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 tight, well-targeted description that clearly states the single purpose and gives a rich set of natural trigger phrases. The only mild gap is that it frames essentially one action rather than several, slightly limiting specificity breadth.

DimensionReasoningScore

Specificity

Names a concrete action — "Harvest every `ponytail:` comment in the codebase into a debt ledger" — plus boundary ("One-shot report, changes nothing"), which is specific to the niche rather than vague, though it centers on a single core action rather than enumerating several.

4 / 5

Completeness

Explicitly answers both what (harvest ponytail: comments into a debt ledger, one-shot, changes nothing) and when (concrete 'Use when...' trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

"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'" provides comprehensive natural trigger phrasing including a slash command and multiple paraphrases/synonyms.

5 / 5

Distinctiveness Conflict Risk

The ponytail-debt / ponytail: comment niche is highly specific with distinct triggers, making conflict with other skills minimal.

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