CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-debt

Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

55

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./.openclaw/skills/ponytail-debt/SKILL.md

The canonical home for this skill is ponytail-debt in DietrichGebert/ponytail

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, well-structured, actionable body that gives copy-paste-ready grep and output templates with verification built into the summary. Only minor polish (an example row, removing one redundant line) would push it higher.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining grep or comments; a minor redundancy (restating the `ponytail: <ceiling>, <upgrade path>` convention already implied by the intro) keeps it just short of a 5.

4 / 5

Actionability

Provides an executable grep command, a concrete output-row template, a flagging rule, and a summary line; the only gap is the absence of a literal filled-in example ledger row.

4 / 5

Workflow Clarity

The scan -> format -> flag -> summarize sequence is clear, and the count summary plus no-trigger flagging serve as verification checkpoints for this batch read-only operation; no explicit error-recovery loop prevents a 5.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and three well-organized sections (Scan, Output, Boundaries), matching the rubric's simple-skill allowance for a top score on structure alone.

5 / 5

Total

17

/

20

Passed

Description

46%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 conveys a clear, distinctive purpose but relies on invented jargon and omits an explicit 'when to use' trigger clause. It is serviceable yet would benefit from natural trigger phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases users would actually say (e.g., 'Use when auditing shortcut/tech-debt comments or reviewing deferred work').

Replace or supplement the coined term 'ponytail' in the description with a plain-language synonym so users unfamiliar with the convention can still recognize the trigger.

List one more concrete action (e.g., 'flags rows lacking an upgrade trigger') to raise specificity beyond two actions.

DimensionReasoningScore

Specificity

Names the domain (ponytail: shortcut comments) and a couple of concrete actions ('Harvest... into one debt ledger', 'One-shot report'), but 'deferrals get tracked instead of forgotten' states purpose rather than an additional action, so coverage is not comprehensive.

3 / 5

Completeness

It clearly answers 'what' (harvest markers into a ledger, one-shot report) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

The keywords ('ponytail', 'debt ledger', 'shortcut comment') are coined jargon a user would not naturally say; common natural variations or synonyms are absent.

2 / 5

Distinctiveness Conflict Risk

The coined `ponytail:` comment convention is a clear niche with low conflict risk, though the trigger terms are not natural user phrases, keeping it just below a 5.

4 / 5

Total

12

/

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.

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