Ponytail Audit
Audit a whole repo for over-engineering and get a ranked cut-list
- What
- Audit a whole repo for over-engineering and get a ranked cut-list
- Cost
- Free
- Needs
- none beyond a working agent; read access to the repository you want reviewed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a repo-wide audit skill that scans the whole tree (not just a diff) for over-engineering and returns a ranked list of what to delete, simplify, or replace, biggest cut first. Findings are tagged: `delete` (dead code, speculative features), `stdlib` (hand-rolled things the standard library ships — names the function), `native` (platform already does it — names the feature), `yagni` (single-implementation abstractions, config nobody sets), `shrink` (same logic, fewer lines). Output is one line per finding ending with a net line-count and dependency estimate (`Lean already. Ship.` when there's nothing to cut). It references the sibling `ponytail-review` from the same repo, but defines its own tags and workflow, so it works standalone. By @dietrichgebert, listed here with credit to its creator. Honest caveats: read-only — it lists findings and applies nothing; correctness bugs, security holes and performance are explicitly out of scope, so pair it with a normal review pass; and the audit's taste is opinionated — "over-engineered" is a judgment call, not a measurement. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none beyond a working agent; read access to the repository you want reviewed Install "Ponytail Audit" for me. Audit a whole repo for over-engineering and get a ranked cut-list Repository: https://github.com/dietrichgebert/ponytail/blob/main/skills/ponytail-audit/SKILL.md 1. Fetch the SKILL.md file for the dietrichgebert-ponytail-audit skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "dietrichgebert-ponytail-audit". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.