setup-matt-pocock-skills
Skill1 starsChanged 16 days agoLicence not identifiedView on GitHub
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
195 other projects use a version of this, 168 of them edited; 80 of 165 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 3 the 4 before.
How people change it
80 of 165 edited versions changed its rules, and some changes recur.
Of the 165 edited versions we compared: 21 keep every rule, 64 are an older text, 80 made changes of their own.
Not in older versions
- When Section B ran on GitHub or GitLab, create each configured label the tracker lacks (
gh label create/glab label create).missing from 64 of 64
Rules people drop
- When Section B ran on GitHub or GitLab, create each configured label the tracker lacks (
gh label create/glab label create).dropped by 78 of 80 - If it is installed, ask exactly one question:dropped by 62 of 80
- Section C: Domain docs. Default to single-context (one
GLOSSARY.md+docs/adr/at the repo root). This fits almost every repo; write it without asking.dropped by 62 of 80 - If neither exists, ask the user which one to create; don't pick for them.dropped by 5 of 80
- Never create
AGENTS.mdwhenCLAUDE.mdalready exists (or vice versa); always edit the one that's already there.dropped by 5 of 80 - If
CLAUDE.mdexists, edit it.dropped by 3 of 80 - If an
## Agent skillsblock already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.dropped by 3 of 80 - Look at the current repo to understand its starting state. Read whatever exists; don't assume:dropped by 2 of 80
Rules people add
- Default: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.added by 58 of 80
- If — and only if — the user picked GitHub or GitLab, ask one follow-up:added by 17 of 80
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Cooling: 1 new project took it in the last 4 weeks, 0.3× the 4 weeks before.thin data
Most recently taken up by
- atpaawej/opencode-skillpackword for word, first seen Nov 16, 2026
- devdeepjs/kobayashi-maruword for word, first seen Nov 16, 2026
- zademy/lu-queryedited, first seen Nov 16, 2026
- qelphybox/tg-mcpword for word, first seen Nov 16, 2026
- lhotwll217/owner-operatoredited, first seen Nov 16, 2026
- ArtisanXL/etsy-mcpword for word, first seen Nov 15, 2026
Used with
Projects with it also use writing-beats, decision-mapping and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 56 projects that use this
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 7 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 55 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 58 projects that use this
AnasX7Skillscaffold-exercises
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Also in 57 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 34 projects that use this
- +1 more from Lesani
Other versions195 projects use a version of this.
Word for word · 19
- mattpocock/skills★ 325k100% same
- tt-a1i/matt-skills-with-to-goal★ 192100% same
- QiYueran-source/waymark★ 112100% same
- HiteSit/real-scientist-skills★ 27100% same
- dz114879/skills★ 4100% same
- geoffbremner/skills★ 4100% same
- devdeepjs/kobayashi-maru★ 2100% same
- fabiandistler/agents★ 2100% same
- kwaa/skills★ 2100% same
- qelphybox/tg-mcp★ 2100% same
9 more not listed
Edited · 168
- QuivrHQ/quivr★ 40k96% same
- The-Vibe-Company/quivr★ 40k96% same
- GreyDGL/PentestGPT★ 16k56% same
- ArcReel/ArcReel★ 6.6k99% same
- vinvcn/mattpocock-skills-zh-CN★ 5.8k16% same
- legions-developer/evilcharts★ 3.2k95% same
- bestofjs/bestofjs★ 3.1k95% same
- moeru-ai/xsai★ 66796% same
- devcxl/mattpocock-skills-zh★ 54315% same
- aws/graph-explorer★ 49299% same
158 more not listed
Wrote their own version · 8
- nodetool-ai/nodetool★ 637same name
- stevesolun/ctx★ 583same name
- Boom-Vitt/skills-thai★ 5same name
- Binbin-miao/workbuddy-expert-team★ 1same name
- lstmemery/skills★ 1same name
- Artknighty/skills-ptbr★ 0same name
- Brians-brain/claude-skills★ 0same name
- hmjBill/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 5 are common, 0 are distinctive, and 4 are very specific to this project.
5
Common
Most of the 163 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 163 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

