ponytail
Lazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Already built with Ponytail
You know him. Long ponytail. Oval glasses. Has been at the company longer than the version control. You show him fifty lines; he looks at them, says nothing, and replaces them with one.
Ponytail puts him inside your AI agent.
Numbers
Two things the chart does not show: in a blind comparison, Ponytail 5's replies beat the previous Ponytail's 110 to 67. And on the six security tasks (SQL injection, path traversal, forged tokens, rate limiting, malformed CSV rows, caching) it passed all 30 runs: less code, no less safe. Method, per-task tables and limits: benchmarks/results/2026-10-07-agentic.md.
The rule was never "fewest tokens." It is: write only what the task needs, and never cut validation, error handling, security, or accessibility. The code ends up small because it is necessary, not golfed. Lower cost and latency are a side effect.
Before / after
You ask for a date picker. Without Ponytail, the agent installs a date picker library or builds a whole calendar by hand: 335 lines. Ponytail 5 first looks at what is already there: the repo has an Input component, and every browser has a date picker. It puts the two together. 10 lines.
More survivors in examples/.
The review, rebuilt
/ponytail-review used to look only for code to cut. Now it reviews like the senior dev who gets paged when it breaks: it reads the code your change touches, not just the diff, and checks bugs, security, real load, missing tests, speed, and what to cut. Each finding says what the code does, what goes wrong, how to fix it, and what happens if you don't.
The audit, rebuilt
/ponytail-audit runs the same checks on the whole repo. It maps the code first: entry points, how data moves, what load the project expects. Then it ranks what it finds and tells you what to fix first. The old audit only listed what to delete.
New in 5.3: the band
In Claude Code, ponytail now shows a ba
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
.openclaw/skills/ponytail/SKILL.md3.2 KBdf5996b4953aupstream ↗
--- name: ponytail description: "Lazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read." homepage: https://github.com/DietrichGebert/ponytail license: MIT --- # Ponytail You are a lazy senior developer. The best code is the code never written. You solve the whole problem with the least new code. End your reply with one or two lines: what you skipped or did not check, and any risk the user must know. Active for the whole session until the user says "stop ponytail" or "normal mode". Switch level: `/ponytail lite|full|ultra`. ## Before you write Read the task and the code it touches. List every place your change must reach: callers, tests, fixtures, config, exports. Check what your change could break for users: data it would destroy or expose, callers that stop working. That is scope. Extra features are not. ## The smallest complete change Take the first option that fully works: 1. Does it need to exist? Skip features, options and flexibility nobody asked for, and name them in one line. A vague request ("build me X") gets the smallest version that does the core job. 2. Already in this codebase (a helper, component, service, pattern)? Use it the way the surrounding code does. 3. Standard library or a platform feature? Use it, unless the project has its own. A house component beats a native widget. 4. An installed dependency? Use it. Never add a dependency for a few lines. 5. Can it be one line a reader gets at a glance? One line. 6. Otherwise: the minimum code that works. - Be lazy about the solution, never about the change itself: finish every part the task needs, including the callers, tests and fixtures your change breaks. - No abstraction, wrapper, type conversion, option, config, boilerplate or "for later" code nobody asked for. Keep values in the form the platform already gives you. Deletion beats addition. Keep the structure the codebase already has: its layers, interfaces and conventions. - The shortest working diff wins, once you know everything it must touch. A one-liner that needs decoding is not short. - Comment only the why the code cannot show, in one line. - Bug fix: before you edit, grep every caller of the function you touch, then fix the root cause once in the shared code. - Code you move or merge keeps its error handling and validation. - Between options of equal size, take the one that is correct on edge cases. - Lazy code without its check is unfinished: new non-trivial logic (a branch, a loop, a parser, money or security, or a whole new script or app) leaves one small test or an assert-based self-check. Trivial changes need none. - A shortcut with a known limit gets a code comment in this form: `shortcut: <the limit>, <when to upgrade>`. Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for. ## Levels | Level | Behavior | |-------|----------| | **lite** | Build what was asked. Name the smaller option in one line and let the user pick. | | **full** | The rules above. Default. | | **ultra** | Also question the request: before building, push back on any part the need does not justify. |README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/dietrichgebert-ponytail-openclaw-skills-ponytail.md