From ponytail
Displays a compact scoreboard showing ponytail's measured benchmark impact on code size, cost, and speed. Useful for a quick summary of ponytail's benefits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ponytail:ponytail-gainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Display this scoreboard when invoked. One-shot: do NOT change mode, write flag
Display this scoreboard when invoked. One-shot: do NOT change mode, write flag files, or persist anything.
The figures are the published benchmark medians (5 everyday tasks: email
validator, debounce, CSV sum, countdown timer, rate limiter; three models:
Haiku, Sonnet, Opus). They are measured, not computed from the current repo.
Source: benchmarks/ and the README.
Render plain ASCII bars. The bar length shows the measured range; the label carries the exact figure:
ponytail gain benchmark median · 5 tasks · 3 models
Lines of code no-skill ████████████████████ 100%
ponytail ██▌················· 6–20% ▼ 80–94%
Cost no-skill ████████████████████ 100%
ponytail █████▌·············· 23–53% ▼ 47–77%
Speed ponytail ▸ 3–6× faster
This repo: /ponytail-debt (shortcuts you deferred)
/ponytail-audit (what's still cuttable)
These are benchmark medians, not this repo. NEVER print a per-repo savings
number ("you saved X lines/tokens here"): the unbuilt version was never
written, so there is no real baseline to subtract from in a live repo. The
only real per-repo figures come from /ponytail-debt (a counted ledger), and
this card points there instead of inventing one.
One-shot display. Edits nothing, changes no mode. "stop ponytail" or "normal mode": revert.
npx claudepluginhub dietrichgebert/ponytail --plugin ponytailRuns a side-by-side benchmark comparing WOZCODE vs vanilla Claude Code on a user's codebase, measuring cost, turn count, and time savings.
Autonomously optimizes code performance using CodSpeed benchmarks, flamegraph analysis, and iterative improvement. Activates on optimization requests, slow functions, or regression mentions.
Enforces Rob Pike's 5 rules for measurement-driven performance optimization, preventing premature code changes without profiling data. Activates on speed complaints or optimization requests.