agentleFS
EclipterEclipter/agents/skills/ponytail-help/SKILL.md

ponytail-help

Skill1 starsChanged 5 days agoMITView on GitHub

Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".

  • Installs packages

46 other projects use a version of this, 41 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use caveman-explore, caveman-help and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JuliusBrusseeSkill

    caveman-explore

    Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.

    Also in 3 projects that use this

  • huangzidaSkill

    caveman-help

    Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

    Also in 5 projects that use this

  • huangzidaSkill

    caveman-commit

    Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

    Also in 6 projects that use this

  • JuliusBrusseeSkill

    caveman-stats

    Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

    Also in 4 projects that use this

  • AnasX7Skill

    gpt-taste

    Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

    Also in 4 projects that use this

  • OpenAISkill

    image-to-code

    Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.

    Also in 4 projects that use this

  • +1 more from JuliusBrussee
  • +2 more from huangzida

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default mode = full, auto-active every session.

    line 45
  2. Very specific:

    If /plugin is not recognized, your Claude Code is out of date.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ponytail Help

Display this reference card when invoked. One-shot, do NOT change mode, write flag files, or persist anything.

Levels

LevelTriggerWhat change
Lite/ponytail liteBuild what was asked, name the smaller option in one line.
Full/ponytailThe smallest complete change, a check where the logic needs one, and a reply that names what was skipped and any risk. Default.
Ultra/ponytail ultraAlso questions the request and pushes back before building.

Level sticks until changed or session end.

Skills

SkillTriggerWhat it does
ponytail/ponytailLazy mode itself: least new code, clear replies that name skipped work and risks.
ponytail-review/ponytail-reviewQuality 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-auditThe same quality review for the whole repo, ranked.
ponytail-debt/ponytail-debtHarvest shortcut: comments into a tracked ledger.
ponytail-gain/ponytail-gainMeasured-impact scoreboard: less code, less cost, more speed.
ponytail-help/ponytail-helpThis 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.

Configure Default Mode

Default mode = full, auto-active every session. Change it:

Environment variable (highest priority):

export PONYTAIL_DEFAULT_MODE=ultra

Config file (~/.config/ponytail/config.json, Windows: %APPDATA%\ponytail\config.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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.