# Ponytail Bundled Skills: Complete Guide to Lazy-Development Utilities > Discover Ponytail's bundled skills: ponytail, ponytail-review, audit, debt, gain, and help. Automate YAGNI, audit code, track debt, and measure gains with intuitive commands. - Repository: [DietrichGebert/ponytail](https://github.com/DietrichGebert/ponytail) - Tags: complete-guide - Published: 2026-08-30 --- **Ponytail ships six bundled skills—`ponytail`, `ponytail-review`, `ponytail-audit`, `ponytail-debt`, `ponytail-gain`, and `ponytail-help`—that enforce YAGNI principles, audit code complexity, track technical debt, and measure optimization gains through intuitive slash commands.** The **Ponytail** repository by DietrichGebert provides a lightweight, extensible framework for lazy software development within AI-assisted coding environments. Each **bundled skill** is defined by a declarative [`SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/SKILL.md) file located under the `skills/` directory and is automatically registered by the plugin runtime to expose functionality via standardized slash commands. These skills implement the project's core philosophy of aggressive simplicity, helping developers eliminate over-engineering through progressive intensity levels. ## Core Bundled Skills in Ponytail Ponytail distributes six primary skills that cover mode enforcement, code review, auditing, debt tracking, impact analysis, and documentation. ### ponytail: The Lazy-Mode Engine The **`ponytail`** skill serves as the central controller for the lazy-development ladder. Defined in [[`skills/ponytail/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail/SKILL.md), this skill enforces a strict hierarchy of simplicity: **YAGNI** → **std-lib** → **native** → **one-line** → **minimal code**. It persists the selected intensity level—**lite**, **full**, or **ultra**—across an entire session unless explicitly disabled. Activate the skill using: - `/ponytail` – Toggles the default full mode. - `/ponytail lite` – Permits standard library usage. - `/ponytail full` – Enforces native implementations only. - `/ponytail ultra` – Aggressively minimizes to single-line solutions. - `stop ponytail` or `ponytail off` – Disables the mode. ### ponytail-review: Over-Engineering Detection The **`ponytail-review`** skill acts as a focused code reviewer that hunts for unnecessary complexity. As specified in [[`skills/ponytail-review/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-review/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-review/SKILL.md), it analyzes the current context and emits one-line suggestions categorized by action tags: `delete`, `stdlib`, `native`, `yagni`, or `shrink`. This allows developers to quickly identify candidates for simplification without manual inspection. Trigger the review with `/ponytail-review`. ### ponytail-audit: Repository-Wide Complexity Analysis For comprehensive analysis, the **`ponytail-audit`** skill performs a recursive scan of the entire codebase. According to [[`skills/ponytail-audit/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-audit/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-audit/SKILL.md), it ranks every detected artefact of unnecessary complexity and produces a prioritized list of recommended deletions and shortcuts. This is useful for spring-cleaning legacy code or preparing for refactoring sprints. Invoke with `/ponytail-audit`. ### ponytail-debt: Technical Debt Ledger The **`ponytail-debt`** skill harvests inline `ponytail:` comments that developers leave in source files to mark temporary shortcuts or known inefficiencies. Defined in [[`skills/ponytail-debt/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-debt/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-debt/SKILL.md), it aggregates these annotations into a tracked ledger, converting scattered TODOs into actionable technical debt items. Run `/ponytail-debt` to view the current debt inventory. ### ponytail-gain: Impact Measurement Quantifying the benefits of lazy-development practices falls to the **`ponytail-gain`** skill. As documented in [[`skills/ponytail-gain/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-gain/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-gain/SKILL.md), this skill provides a scoreboard displaying measured impact in **lines of code**, **bytes**, or **milliseconds** saved during a session. This metric helps teams justify architectural simplifications to stakeholders. Display the scoreboard with `/ponytail-gain`. ### ponytail-help: Command Reference Finally, the **`ponytail-help`** skill offers a non-destructive quick-reference card. Located at [[`skills/ponytail-help/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-help/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail-help/SKILL.md), it lists all available modes, intensity levels, and auxiliary skills without modifying the active configuration. It responds to both `/ponytail-help` and the natural language phrase "ponytail help". ## Skill Architecture and Runtime Registration Understanding how these skills are loaded requires examining the build and hook infrastructure. The plugin uses a declarative architecture where each skill is a self-contained markdown package. ### SKILL.md Structure and Parsing Each skill definition resides in a [`SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/SKILL.md) file containing YAML front-matter—specifying `name`, `description`, `argument-hint`, and `license`—followed by a markdown body that defines behavior, triggers, and output formats. The build script [[`scripts/build-openclaw-skills.js`](https://github.com/DietrichGebert/ponytail/blob/main/scripts/build-openclaw-skills.js)](https://github.com/DietrichGebert/ponytail/blob/main/scripts/build-openclaw-skills.js) parses these files to generate the OpenClaw skill package (`.openclaw/skills/`). ### Plugin Manifest Integration The generated skills are advertised through [[`plugin.json`](https://github.com/DietrichGebert/ponytail/blob/main/plugin.json)](https://github.com/DietrichGebert/ponytail/blob/main/plugin.json) and loaded by the runtime hook [[`hooks/ponytail-instructions.js`](https://github.com/DietrichGebert/ponytail/blob/main/hooks/ponytail-instructions.js)](https://github.com/DietrichGebert/ponytail/blob/main/hooks/ponytail-instructions.js). This hook specifically loads the primary [[`skills/ponytail/SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail/SKILL.md)](https://github.com/DietrichGebert/ponytail/blob/main/skills/ponytail/SKILL.md) to determine and display the current active mode during initialization. ### Extensibility Model Adding new capabilities requires only creating a new folder under `skills/` with a valid [`SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/SKILL.md). The [[`build-openclaw-skills.js`](https://github.com/DietrichGebert/ponytail/blob/main/build-openclaw-skills.js)](https://github.com/DietrichGebert/ponytail/blob/main/scripts/build-openclaw-skills.js) script automatically discovers and registers new skills during the next build cycle, making the system highly extensible without core code changes. ## Command Usage Examples The following slash commands demonstrate typical workflows for the **bundled skills in Ponytail**: Activate full lazy mode: ```bash /ponytail ``` Switch to ultra-intensity for aggressive minimization: ```bash /ponytail ultra ``` Review the current file for over-engineering: ```bash /ponytail-review ``` Audit the entire repository: ```bash /ponytail-audit ``` List harvested technical debt: ```bash /ponytail-debt ``` Check optimization gains: ```bash /ponytail-gain ``` Display the help card: ```bash /ponytail-help ``` ## Summary - **Ponytail** provides six bundled skills—`ponytail`, `ponytail-review`, `ponytail-audit`, `ponytail-debt`, `ponytail-gain`, and `ponytail-help`—each defined by a [`SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/SKILL.md) file in the `skills/` directory. - The core **`ponytail`** skill enforces YAGNI principles across three intensity levels (lite, full, ultra) and persists the selected mode across sessions. - Auxiliary skills handle specialized tasks: code review, repository auditing, debt tracking, impact measurement, and documentation. - Skills are automatically registered by the runtime via [`scripts/build-openclaw-skills.js`](https://github.com/DietrichGebert/ponytail/blob/main/scripts/build-openclaw-skills.js) and exposed through standardized slash commands. - The architecture supports drop-in extensibility: new skills are automatically discovered by the build script without modifying core plugin logic. ## Frequently Asked Questions ### How do I activate a specific Ponytail skill? Each skill is triggered by its corresponding slash command. For example, type `/ponytail ultra` to activate the core skill in ultra mode, or `/ponytail-audit` to run a repository-wide analysis. The commands are registered automatically when the plugin loads in your IDE. ### What is the difference between ponytail-review and ponytail-audit? **`ponytail-review`** performs a focused analysis on the current file or selection, emitting immediate one-line suggestions for simplification. **`ponytail-audit`**, conversely, scans the entire repository recursively to rank all instances of unnecessary complexity, producing a comprehensive prioritized list of deletions and shortcuts. ### How does Ponytail maintain state across coding sessions? The core **`ponytail`** skill persists the selected intensity level—lite, full, or ultra—across responses within a session. To disable lazy mode and return to standard behavior, explicitly issue the command `stop ponytail` or `ponytail off`. ### Can I create custom skills for the Ponytail framework? Yes. The plugin architecture supports drop-in extensions. Create a new folder under `skills/` containing a properly formatted [`SKILL.md`](https://github.com/DietrichGebert/ponytail/blob/main/SKILL.md) file with front-matter and behavior definitions. The [[`build-openclaw-skills.js`](https://github.com/DietrichGebert/ponytail/blob/main/build-openclaw-skills.js)](https://github.com/DietrichGebert/ponytail/blob/main/scripts/build-openclaw-skills.js) script will automatically detect and register your custom skill during the build process.