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.
Install
/plugin marketplace add DietrichGebert/ponytailThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add DietrichGebert/ponytail --skill ponytailgit clone --depth 1 https://github.com/DietrichGebert/ponytail.git /tmp/ponytail
mkdir -p ~/.claude/skills
cp -r /tmp/ponytail/.openclaw/skills/ponytail ~/.claude/skills/ponytailPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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.Details
- Skill name
ponytail- Repository
- DietrichGebert/ponytail
- Path
.openclaw/skills/ponytail/SKILL.md- License
- MIT
- Repo updated
- 29 October 2026
FAQ
What does the Ponytail skill do?
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.
How do I install the Ponytail skill?
Claude Code plugin: /plugin marketplace add DietrichGebert/ponytail. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Ponytail popular?
It lives in DietrichGebert/ponytail, which has 181,225 GitHub stars and 9,958 forks.
Related skills
Ponytail
181kDietrichGebert/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.
Ponytail Audit
181kDietrichGebert/ponytail
Quality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.
Ponytail Audit
181kDietrichGebert/ponytail
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.
Unified Memory
294kaffaan-m/ECC
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
Cold Email
58kcoreyhaines31/marketingskills
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up sequence," "nobody's replying," "email deliverability," "sending domains," "warm up inboxes," "LinkedIn outreach," "connection request message," "multichannel sequence," "cadence," "cold call," "voicemail," "handle replies," "AI SDR," "teardown outreach," or "product-led outbound." Send from secondary domains, verify lists first
Strategic Compact
294kaffaan-m/ECC
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.