Ponytail Help
Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".
Get the complete skill folder, including its scripts and reference files.
·
When to use this skill
Use Ponytail Help when an AI agent needs a reusable SKILL.md workflow for this job: Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".
When not to use it
Skip Ponytail Help when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/ponytail-help # Save SKILL.md to ~/.claude/skills/ponytail-help/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ponytail-help/SKILL.md. For a shared project, commit the folder at .claude/skills/ponytail-help/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Ponytail Help skill for this task: Use Ponytail Help when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 75/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Ponytail Help
Display this reference card when invoked. One-shot, do NOT change mode, write flag files, or persist anything.
## Levels
| Level | Trigger | What change | |-------|---------|-------------| | **Lite** | `/ponytail lite` | Build what was asked, name the smaller option in one line. | | **Full** | `/ponytail` | The smallest complete change, a check where the logic needs one, and a reply that names what was skipped and any risk. Default. | | **Ultra** | `/ponytail ultra` | Also questions the request and pushes back before building. |
Level sticks until changed or session end.
## Skills
| Skill | Trigger | What it does | |-------|---------|--------------| | **ponytail** | `/ponytail` | Lazy mode itself: least new code, clear replies that name skipped work and risks. | | **ponytail-review** | `/ponytail-review` | Quality review of a diff: bugs, security, load, missing tests, speed, what to cut. Each finding says what goes wrong and how to fix it. | | **ponytail-audit** | `/ponytail-audit` | The same quality review for the whole repo, ranked. | | **ponytail-debt** | `/ponytail-debt` | Harvest `shortcut:` comments into a tracked ledger. | | **ponytail-gain** | `/ponytail-gain` | Measured-impact scoreboard: less code, less cost, more speed. | | **ponytail-help** | `/ponytail-help` | This card. |
In Codex CLI and the IDE extension, invoke skills with `$ponytail:ponytail`, `$ponytail:ponytail-review`, or `$ponytail:ponytail-help`. Claude Code and OpenCode use the slash-command forms above (OpenCode ships all six as slash commands).
## Deactivate
Say "stop ponytail" or "normal mode". Resume anytime with `/ponytail`. `/ponytail off` also works.
## Band (Claude Code)
`/ponytail band` hides the band above the prompt, the same command brings it back. `/ponytail band on` and `/ponytail band off` set it directly. The level stays. `/ponytail band import` adds your past Claude Code sessions (cost, agent time, tokens) to the board.
## Configure Default Mode
Default mode = `full`, auto-active every session. Change it:
**Environment variable** (highest priority): ```bash export PONYTAIL_DEFAULT_MODE=ultra ```
**Config file** (`~/.config/ponytail/config.json`, Windows: `%APPDATA%\ponytail\config.json`): ```json { "defaultMode": "lite" } ```
Set `"off"` to disable auto-activation on session start, activate manually with `/ponytail` when wanted.
Resolution: env var > config file > `full`.
## Update
Enable auto-update once: open `/plugin`, go to Marketplaces, pick ponytail, Enable auto-update. Claude Code then pulls new versions at startup (run `/reload-plugins` when it prompts). Manual refresh: `/plugin marketplace update ponytail` then `/reload-plugins`.
If `/plugin` is not recognized, your Claude Code is out of date. Update it (`npm install -g @anthropic-ai/claude-code@latest`, or `brew upgrade claude-code`) and restart. Other hosts use their own update flow.
## More
Full docs + examples: https://github.com/DietrichGebert/ponytail
Intended uses
- Use Ponytail Help when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.