A FIELD GUIDE TO BETTER CODING AGENTS

AGENT
SKILLS

11 open-source skill collections.
For the things you wish your coding agent
already knew how to do.

↓
For Claude, Codex & curious humans.Explore. Install. Make something.
Better questionsSharper interfacesCleaner code

THE COLLECTION

Eleven tools. Eleven different ways to work.
New to skills? Start here.

Poster 01: Matt Pocock Skills — make engineering judgement reusable.
Save SVG ↓
01 · MIT · Shell277,047 stars*

Matt Pocock Skills

mattpocock/skills ↗

A collection of focused playbooks for recurring engineering work: clarify the request, debug methodically, improve the architecture and check that the result holds up.

How to use it
  • Use /grill-me to sharpen an unclear brief.
  • Use /tdd to work in small, verified steps.
  • Skills are small enough to adapt to your own workflow.
Try first

Start with /grill-me before a feature that feels underspecified.

npx skills@latest add mattpocock/skills
Poster 02: Ponytail — prefer the smallest sound solution.
Save SVG ↓
02 · MIT · JavaScript155,948 stars*

Ponytail

DietrichGebert/ponytail ↗

A “do we need this?” check before new code. It walks the agent through simpler options first, while keeping validation, security, errors and accessibility in view.

How to use it
  • Reuse what the project already has.
  • Prefer built-in platform features and standard libraries.
  • Add custom code only when the simpler options do not fit.
Try first

Ask for a small feature and see whether a native control already does the job.

codex plugin marketplace add DietrichGebert/ponytail
codex plugin add ponytail@ponytail
Poster 03: UI UX Pro Max — choose a design direction before building.
Save SVG ↓
03 · MIT · Python133,327 stars*

UI UX Pro Max

nextlevelbuilder/ui-ux-pro-max-skill ↗

A searchable design reference that helps an agent choose a visual direction before it builds. It brings together styles, palettes, type pairings and practical interface rules.

How to use it
  • Explore styles and font combinations by product type.
  • Bring accessibility, hierarchy and platform needs into the brief.
  • Works across a range of front-end and mobile stacks.
Try first

Ask it to pick a coherent style and type palette for a real page before generating UI.

npm install -g ui-ux-pro-max-cli
uipro init --ai codex
Poster 04: Graphify — map how parts of a codebase connect.
Save SVG ↓
04 · Apache-2.0 · Python124,051 stars*

Graphify

Graphify-Labs/graphify ↗

Turns a codebase and its supporting material into a browsable knowledge graph, so you can trace relationships instead of guessing where a behaviour lives.

How to use it
  • Connect source code with docs, schemas and configuration.
  • Mark direct extraction separately from inferred links.
  • Open a generated graph and follow the connections.
Try first

Run /graphify in a repository you are still learning.

uv tool install graphifyy
graphify install
Poster 05: Caveman — say the useful thing with fewer words.
Save SVG ↓
05 · MIT skill · Go109,993 stars*

Caveman

JuliusBrussee/caveman ↗

A concise-response style for coding agents. It trims conversational padding while leaving code, paths, commands and technical details intact.

How to use it
  • Choose a lighter or more compressed voice.
  • Keep code and error details readable.
  • Optional tooling can also reduce noisy command output.
Try first

Ask a coding question, then compare the answer with /caveman lite.

npx skills add JuliusBrussee/caveman -g
Poster 06: Addy Osmani Skills — take a feature from definition through review.
Save SVG ↓
06 · MIT · JavaScript101,538 stars*

Addy Osmani Skills

addyosmani/agent-skills ↗

A set of repeatable engineering workflows across the feature lifecycle: define the problem, plan the work, build, verify and review.

How to use it
  • Separate planning from implementation.
  • Keep constraints and performance in scope.
  • Use lifecycle skills alongside smaller task-specific ones.
Try first

Use /spec to describe a feature, then /plan before building.

npx skills@latest add addyosmani/agent-skills
Poster 07: Taste Skill — add intentional visual choices to generated interfaces.
Save SVG ↓
07 · MIT · JavaScript92,835 stars*

Taste Skill

Leonxlnx/taste-skill ↗

A set of focused design skills for steering the visual character of generated interfaces, from layout and typography to motion and finish.

How to use it
  • Set visual variance, motion and density to suit the brief.
  • Use a style direction as a constraint, not decoration.
  • Audit an existing page before changing it.
Try first

Give it a generic page you already have and ask for a redesign with a clear audience and mood.

npx skills add https://github.com/Leonxlnx/taste-skill
Poster 08: Understand Anything — explore a codebase as a connected map.
Save SVG ↓
08 · MIT · TypeScript85,359 stars*

Understand Anything

Egonex-AI/Understand-Anything ↗

Creates an interactive map of a project, with explanations and ways to ask questions about its structure and behaviour.

How to use it
  • Explore files and relationships visually.
  • Ask about flows or the impact of a change.
  • Generate guided tours and onboarding notes.
Try first

Start with /understand, then open the generated project map.

/plugin marketplace add Egonex-AI/Understand-Anything
/plugin install understand-anything
Poster 09: Awesome Claude Skills — browse a directory of tools by task.
Save SVG ↓
09 · Curated directory76,552 stars*

Awesome Claude Skills

ComposioHQ/awesome-claude-skills ↗

A browsable directory for when you know the kind of task you want help with but have not found the right skill yet.

How to use it
  • Browse by areas such as writing, data, security and productivity.
  • Compare official and community resources.
  • Check the project README for current install and compatibility details.
Try first

Search for the tool or type of work you do most often.

Browse the repository README
Poster 10: Archify — turn a system description into an architecture map.
Save SVG ↓
10 · MIT · JavaScript78,083 stars*

Archify

tt-a1i/archify ↗

Turns a short system description or an existing repository into an interactive architecture diagram that can be explored and shared.

How to use it
  • Map architecture, sequences, data flow or a lifecycle.
  • Trace diagram elements back to source files when available.
  • Export or share the standalone visual result.
Try first

Describe a simple request flow and ask for a sequence diagram.

npx skills add tt-a1i/archify -g
Poster 11: Impeccable — give your agent a shared language for design critique.
Save SVG ↓
11 · Apache-2.0 · JavaScript77,042 stars*

Impeccable

pbakaus/impeccable ↗

A shared design vocabulary for directing and critiquing interface work. Its commands help make feedback more specific than “make it pop”.

How to use it
  • Ask for focused changes such as polish, typeset or harden.
  • Audit common visual and accessibility issues.
  • Save product context so follow-up requests have a consistent direction.
Try first

Run /impeccable audit on a page before asking for a redesign.

npx impeccable install

*Stars checked directly against the GitHub API on 5 October 2026. Counts change over time. The collection follows Davecto’s original selection; descriptions and artwork are by Bruno Silva. Check each repository’s README for current installation instructions.

Skills 101

A playbook your agent can reach for.

A skill is a folder of instructions—usually centred on a SKILL.md file—that tells an AI agent how to approach a particular kind of work. Some also include scripts, templates or reference material.

The agent can load the detailed instructions when a task calls for them. That makes a skill different from pasting the whole playbook into every prompt.

01Describe the job

Tell your agent what you need.

02Use the right playbook

The skill adds task-specific steps and context.

03Review the result

You remain responsible for what gets run or shipped.

Where to start

Pick the problem
you have today.

You do not need all eleven at once. Try one that fits a task you already understand, then decide whether it earns a place in your setup.

If your agent misses the brief

Make the request clearer.

Try the grilling workflows in Matt Pocock’s collection, then use Addy Osmani’s planning steps to shape the work.

Matt Pocock ↗Addy Osmani ↗
If the answers or code feel bloated

Try simpler, shorter work.

Ponytail checks whether new code needs to exist. Caveman trims conversational padding. They solve different problems.

Ponytail ↗Caveman ↗

Looking for something outside these examples? Browse the curated directory ↗

Before you install

Read first.
Then decide.

01

Read the instructions.

A skill affects how an agent works. Skim its SKILL.md and make sure you understand the steps.

02

Inspect scripts and hooks.

Before approving code that runs locally, look at what it does and which files or services it can touch.

03

Choose one install path.

Do not install the same repository both as a plugin and through a skills manager unless the project tells you to.

04

Start with one.

Overlapping instructions can conflict. Try one skill on a task you can review, then add another if it helps.