Report · marked 26 Aug 2026

mattpocock/skills

An agent can work here, but it will waste turns finding its footing.

Shell · 236,870 stars · 164 files · branch main

68 /100 B

Instructions 15/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 12/14Whether an agent can install the project and get it running without a human. Losing marks on pinned runtime version.Verification loop 10/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist and test command is discoverable.Context economy 19/20Whether the repo fits in a context window, or fights it. Losing marks on .gitignore hygiene.Navigability 9/10How quickly anything new can orient itself. Losing marks on repository description.

Higher is better. Accent marks what is costing you most.

Fix these first

Test command is discoverable

Add a `test` script or a `test` target that runs the whole suite with no arguments. The convention is the interface — an agent tries `npm test` and `make test` before it tries reading your CI config.

Instruction quality

Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.

Lint and format rules

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

The full marking

Every deduction below names the file or setting it came from.

Instructions 15/27 B-

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: CLAUDE.md

✗Instruction quality 0/12

Present but too thin to change an agent's behavior.

Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 12/14 A

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6

package-lock.json pins the dependency tree.

Found package-lock.json

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

package.json scripts (changeset, version, check-plugin-version)

scripts/ directory

–Environment config n/a

Not applicable — this reads as a library, with no environment to configure.

✗Pinned runtime version 0/2

No pinned runtime version.

Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.

–Reproducible environment n/a

Not applicable — a library doesn't need a container to be worked on.

Verification loop 10/25 C

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✗Tests exist 6/8

1 test file against 7 source files.

e.g. docs/engineering/to-spec.md

✗Test command is discoverable 0/7

There's no obvious way to run the tests. Even if tests exist, an agent won't reliably find the entry point.

✓Continuous integration 4/4

1 GitHub Actions workflow define what "passing" means.

✗Lint and format rules 0/3

No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

✗Static type checking 0/3

No static type checking.

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

Context economy 19/20 A+

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✗.gitignore hygiene 2/3

.gitignore has only 2 rules.

Start from a standard template for your stack. It prevents the previous problem before it happens.

✓File sizes fit in context 6/6

No source file is large enough to crowd out a context window.

✓Repository weight 5/5

About 1.5MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for mattpocock/skills

# AGENTS.md

Skills for Real Engineers. Straight from my .agents directory.

## Setup

```
npm ci
```

## Commands

```
npm run changeset
npm run version
npm run check-plugin-version
```

## Layout

- `skills/`  4 source files
- `scripts/` 3 source files

## Conventions

- Tests live alongside the code they cover, following `docs/engineering/to-spec.md`.
- CI defines what passing means. See `.github/workflows/release.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/mattpocock/skills.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/mattpocock/skills.svg)](https://agentreadme.com/mattpocock/skills)

Other Shell repositories, marked

obra/superpowers 68 B ohmyzsh/ohmyzsh 46 C msitarzewski/agency-agents 42 C d3/d3 68 B nvm-sh/nvm 77 B+ tw93/Mole 88 A

All Shell repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in