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.

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-crafted skill body: concrete commands and templates, a clear single-task workflow, and clean section organization with no redundant explanation. It assumes Claude's competence and respects the context window.

DimensionReasoningScore

Conciseness

Lean and token-efficient with no padding and no explanations of concepts Claude already knows; every line earns its place.

3 / 3

Actionability

Provides a copy-paste-ready grep command, an explicit per-row output template, a concrete `git blame` enhancement, and a defined empty-state message — fully executable guidance.

3 / 3

Workflow Clarity

A simple single-purpose read-only skill whose single action is unambiguous: scan, format rows, flag no-trigger rows, summarize — with no destructive operations requiring validation checkpoints.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear sections (Scan, Output, Boundaries) that satisfy the simple-skill allowance for a top score.

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 model description: concrete capabilities, explicit and natural trigger terms, complete what-and-when guidance, and a clearly distinct niche. Third-person voice is maintained throughout. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — harvesting `ponytail:` comments across the codebase and aggregating them into a debt ledger — with no vague language.

3 / 3

Completeness

Explicitly answers both what it does ('Harvest every ponytail: comment into a debt ledger') and when to use it via a clear 'Use when the user says...' clause with multiple triggers.

3 / 3

Trigger Term Quality

Provides a strong set of natural phrases a user would actually say ('ponytail debt', 'what did ponytail defer', 'list the shortcuts', 'ponytail ledger') plus a slash-command trigger.

3 / 3

Distinctiveness Conflict Risk

The niche is highly specific — a single convention's comment markers — with distinctive triggers that are unlikely to collide with other skills.

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.