agentsclimarketplace

Ponytail

Skill aarshsharma2803-stack/optimusprime/skills/ponytail

The session state protocol for AI coding. Hook-level scope enforcement, cross-session memory, contradiction detection, and predictive context - Claude is stateless, your project isn't.

Install
npx -y skills add aarshsharma2803-stack/optimusprime --skill ponytail

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Code minimalism — no premature abstractions, no speculative features, smallest correct implementation only. Auto-activates when complexity budget is minimal or user asks for simpler/smaller code. Trigger: complexity_budget:minimal, goal contains refactor/simplify/minimize/clean/slim, or user says "keep it simple", "no abstractions", "smaller diff".

SKILL.md

2.4 KB, as published. Nobody here has run it

Write the smallest correct implementation. No extra.

Rules

  • No abstraction until the same logic appears 3+ times in the same codebase
  • No optional parameters that nothing calls with a non-default value yet
  • No helper function for a single call site — inline it
  • No "future-proof" wrapper around something that already works
  • No config knob for a value that never actually varies
  • Delete more than you write when refactoring
  • Three similar lines beats a premature abstraction
  • Trust the framework — don't wrap what already works

Before/after

Not:

class RetryStrategy:
    def __init__(self, max_attempts=3, backoff_fn=None):
        self.max_attempts = max_attempts
        self.backoff_fn = backoff_fn or (lambda i: 2 ** i)

def fetch_with_retry(url, strategy=None):
    strategy = strategy or RetryStrategy()
    for i in range(strategy.max_attempts):
        ...

Yes:

def fetch_with_retry(url, max_attempts=3):
    for i in range(max_attempts):
        try:
            return requests.get(url)
        except requests.RequestException:
            if i == max_attempts - 1:
                raise
            time.sleep(2 ** i)

Nobody asked for pluggable backoff strategies. When someone does, add it then — with a real second use case in hand, not a hypothetical one.

When adding code

Ask: "What is the minimum that makes this work?" Write that. Not "what's the minimum that also handles cases nobody has hit yet."

When reviewing code

Ask: "What can be deleted without breaking anything?" Delete that. Unused parameters, dead branches, config that's always the same value — gone.

Interaction with other Auto Bots

  • If Superpowers is also active (rare — they trigger on opposite complexity signals): Superpowers governs planning rigor, Ponytail governs implementation size. A well-planned small change is not a contradiction.
  • Independent of Caveman Bot — Ponytail shapes code, Caveman shapes prose. Both can run at once.

Persistence

Active for the full session once triggered. Off only: "stop ponytail" or "normal mode".

Gives 0 of the 12 instructions most refactoring skills give

Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06

  • run tests after each changein 59 of 521, across 56 files
  • write tests before refactoringin 27 of 521, across 24 files
  • preserve external behaviorin 26 of 521, across 22 files
  • remove dead codein 25 of 521, across 24 files
  • make small incremental changesin 20 of 521, across 17 files
  • break the implementation into tiny commitsin 18 of 521, across 5 files
  • ask the user about alternative optionsin 17 of 521, across 4 files
  • create a GitHub issue with the planin 17 of 521, across 4 files
  • explore the repository to verify assertionsin 17 of 521, across 4 files
  • interview the user about the refactorin 16 of 521, across 3 files
  • check the codebase for test coveragein 16 of 521, across 3 files
  • refactor one thing at a timein 16 of 521, across 12 files

Said here and by no other author read

  • write the smallest correct implementation
  • delete more than you write when refactoring
  • trust the framework without wrapping it
  • ask what minimum makes it work before writing
  • prefer three similar lines over premature abstraction
  • add abstraction only after logic appears three times

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.