CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

73

Quality

92%

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 in DietrichGebert/ponytail

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 exceptionally tight instruction skill: every token earns its place, the decision procedure is concrete and prioritized, and verification requirements are built in. Sections are well organized for a single-file skill with no bundle files to reference.

DimensionReasoningScore

Conciseness

Lean and efficient: every line is a load-bearing rule ('That is scope. Extra features are not.'; 'Deletion beats addition.'), with no explanation of concepts Claude already knows and no padding anywhere in the ~41-line body.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a six-step decision ladder in priority order, a verbatim comment template ('shortcut: <the limit>, <when to upgrade>'), a concrete verification rule, and a levels table with a switch command.

5 / 5

Workflow Clarity

Clear sequence — scope in 'Before you write', then the decision ladder, then rules and levels — with an explicit verification checkpoint ('new non-trivial logic... leaves one small test or an assert-based self-check') and scope verification ('grep every caller'). Not a destructive/batch workflow, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references; the body is well-organized into 'Before you write', 'The smallest complete change', and 'Levels' sections, which satisfies the simple-skill exception for full marks.

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: concise, concrete, third-person, with an explicit 'Use when' clause carrying natural trigger phrases. Its only weaknesses are a few missing synonyms in the trigger list and the deliberately broad 'any coding task' applicability, which raises mild conflict risk with other coding skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete specifics — 'the smallest change that fully solves the task', 'a reply a busy human understands in one read', plus four task types (writing, fixing, reviewing, choosing dependencies) and three levels. Falls just short of comprehensive action coverage.

4 / 5

Completeness

Explicitly answers both what ('the smallest change that fully solves the task, and a reply a busy human understands in one read') and when ('Use on any coding task... and when the user says...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say: 'ponytail', 'be lazy', 'simplest solution', 'yagni', 'over-engineering', 'bloat'. A few common synonyms (KISS, 'keep it simple', 'overcomplicated') are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Unique trigger vocabulary ('ponytail', 'yagni', 'be lazy') gives it a clear niche with mostly distinct triggers, but 'Use on any coding task' is broad and creates minor overlap risk with closely related coding skills such as code review or simplification.

4 / 5

Total

17

/

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.

Validation — 15 / 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

graphif/project-graph

Path

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