CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ponytail

External agent skill (MIT, github.com/DietrichGebert/ponytail). Forces the laziest solution that actually works: question whether the task needs to exist at all (YAGNI), reuse what is already in the codebase, reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Climb the ladder on every coding task — writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Supports intensity levels: lite, full (default), ultra. Never cut validation, error handling, security, or accessibility.

Quality

82%

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

81%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 well-structured, highly actionable behavior skill: the ladder, bug-fix rule, output pattern, and intensity table give concrete, executable guidance with explicit validation and feedback loops. The main defect is redundancy — a duplicated frontmatter block inside the body — plus light persona padding, which costs token efficiency without costing clarity.

Suggestions

Delete the duplicated inner YAML block in the 'skill:custom-start' section — it re-states name, description, and license verbatim and consumes ~15% of the body.

Trim persona flourishes in the opening ('seen every over-engineered codebase and been paged at 3am') to one short line to tighten token efficiency.

DimensionReasoningScore

Conciseness

The core guidance is tight and assumes competence, but the inner 'skill:custom-start' block repeats the full frontmatter (name, description, license) verbatim — roughly 18 of ~125 body lines of pure redundancy — alongside persona flourishes ('been paged at 3am', 'seen every over-engineered codebase'). Mostly efficient with unnecessary content that could be trimmed; not 2 because the actual instruction content is dense and earns its tokens.

3 / 5

Actionability

Fully concrete and executable for an instruction-style skill: the seven-rung ladder, real code (`@lru_cache(maxsize=1000)`, `<input type="date">` over a picker lib), an exact comment format (`# ponytail: global lock, per-account locks if throughput matters`), an output pattern (`[code] → skipped: [X], add when [Y].`), and worked lite/full/ultra responses for a cache example. Specific examples cover the common cases; not 4 because there are no material gaps.

5 / 5

Workflow Clarity

The process is an explicit ordered checklist ('Stop at the first rung that holds', rungs 1–7) with a mandatory comprehension pre-step ('Read the task and the code it touches first, trace the real flow end to end'), a validation requirement ('leaves ONE runnable check behind'), and a user feedback loop ('Ship the lazy version and question it in the same response... Need full X? Say so'). Clear sequence with explicit validation and recovery; not 4 because checkpoints are present, not merely implied.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is organized into clear, well-labeled sections (Persistence, The ladder, Rules, Output, Intensity, When NOT to be lazy, Boundaries) with no nested-reference problem. Good structure with a minor gap: the duplicated inner frontmatter block inside the body is misplaced content; not 5 because that redundancy and the >50-line length leave slight organization room, not 3 because nothing that belongs in a separate file is inlined.

4 / 5

Total

17

/

20

Passed

Description

76%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 specific, action-rich description with an explicit task-type trigger and useful guardrails ('Never cut validation, error handling, security, or accessibility'). Its weaknesses are the overly broad 'every coding task' trigger scope and the absence of the natural user phrases (over-engineering, bloat, lazy mode) that appear only in the body. The leading 'External agent skill (MIT, github.com/...)' metadata adds noise without capability information.

Suggestions

Narrow the trigger or add differentiating phrases, e.g. 'Use when the user complains about over-engineering, bloat, boilerplate, or unnecessary dependencies', to reduce conflict with general coding and code-review skills.

Fold the natural trigger terms already present in the body ('be lazy', 'lazy mode', 'simplest solution', 'do less', 'shortest path') into the description to lift trigger term quality and completeness.

Drop the 'External agent skill (MIT, github.com/...)' prefix or move it to a license field so the description leads with capability.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'question whether the task needs to exist at all (YAGNI), reuse what is already in the codebase, reach for the standard library before custom code, native platform features before dependencies, one line before fifty' — plus intensity levels (lite/full/ultra) and an explicit exclusion list. This matches the comprehensive-coverage anchor; not 4 because no meaningful capability gaps remain.

5 / 5

Completeness

The 'what' is explicit (the lazy-ladder behaviors) and the 'when' is present as 'Climb the ladder on every coding task — writing, adding, refactoring, fixing, reviewing, or designing code', so it clears the cap-at-3 rule. Not 5 because it lacks concrete user-phrase triggers (e.g., 'when the user complains about over-engineering or bloat') that would make the 'when' fully explicit.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('YAGNI', 'refactoring', 'fixing', 'reviewing', 'libraries or dependencies') but omits common trigger phrasing like 'over-engineering', 'boilerplate' complaints, 'lazy', or 'simplest solution' that the body itself lists. Good coverage with a few natural terms missing; not 5 because those synonyms are absent, not 3 because coverage goes well beyond a bare domain mention.

4 / 5

Distinctiveness Conflict Risk

The minimalism/laziness niche is distinctive, but the stated trigger 'on every coding task' is broad and would collide with general coding, refactoring, and code-review skills. Somewhat specific yet real overlap risk with similar skills; not 4 because 'every coding task' claims near-universal scope rather than minor overlap.

3 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

diegosouzapw/OmniRoute

Path

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.