Matt Pocock skills
Choosing a Matt Pocock skills setup: subscribe, adapt or inspect first
Compare managed distribution, editable copies and source inspection by ownership and verification needs, without inventing a universal agent-workflow winner.
What you will learn
- Compare approaches against the same need
- Use the actual set, not the repository headline
- Choose an evaluation you can reverse
Before you start
- Basic repository, issue-tracker and test concepts
- An understanding that instructions and permission are different
Choose an adoption model and trace its files, authority boundaries and verification evidence.
Key takeaways
- Choose based on ownership and task boundaries.
- Plugin, development links and tree listing are different inventories.
- A reversible trial is more useful than an unsupported ranking.
Compare approaches against the same need
A managed bundle suits a team that wants the promoted upstream set with fewer locally maintained instruction forks. Editable copies suit a team that needs repository-specific terminology, constraints or workflow adaptations. Source inspection alone can be the right first step when the team has not yet identified a failure mode worth addressing. These choices differ in responsibility, not simply convenience.
Write down the acceptance condition before comparing options. For example, a team may need consistent issue briefs without permitting automatic issue closure. Evaluate whether the selected skills and host permissions support that boundary. A larger catalogue or a more polished installation screen does not answer the authorization question.
Use the actual set, not the repository headline
At the pinned revision, the plugin explicitly enumerates 25 promoted directories. The maintainer linker would select 33 skills under its exclusions, including in-progress work, while the listing script finds 37 skill files across the tree. The latter two counts are source-derived inventory results; the linker was not executed. Comparing them as equivalent products would mislead a reader.
For a specific task, identify the entry point, its reusable dependencies and the project conventions it requires. A copied entry point without the discipline it references may be an incomplete adoption. On the other hand, importing unrelated experimental skills increases the material your team must review without necessarily improving that task.
Choose an evaluation you can reverse
Start with a small project, retain the original instructions and record the resolved revision. Compare outcomes against a no-skill baseline and review the changes needed to adapt the workflow. Do not install both distribution routes just to make the comparison simultaneous; that can obscure which version of a same-name skill the host selected.
This review does not establish that the collection outperforms another repository, an agent’s built-in behavior or a human-led process. It provides source-specific selection criteria and a bounded maintenance-script test. A production choice should follow your own task evidence, compatibility checks and update policy rather than an invented ranking.
Implementation steps
- 1
State the exact behavior and actions you want to permit.
- 2
Choose one distribution ownership model.
- 3
Inspect the selected skill and its dependencies.
- 4
Compare a reversible trial with the same-task baseline.
Copy-ready example
{
"criteria": ["ownership", "resolved revision", "task fit", "permitted actions", "update review"],
"pluginInventory": 25,
"developmentLinkInventoryFromSource": 33,
"treeSkillFiles": 37,
"universalWinner": null,
"comparativeSuccessRate": null
}Frequently asked questions
Should I choose the option with the most skills?
Not automatically. Review the subset and dependencies relevant to your actual workflow.
Is the development linker a third recommended distribution?
No. It is included here to explain a source-level inventory difference, not as a general installation recommendation.
Sources
- README.mdSource checked 2026-09-08
- .claude-plugin/plugin.jsonSource checked 2026-09-08
- scripts/link-skills.shSource checked 2026-09-08
- scripts/list-skills.shSource checked 2026-09-08
- .agents/adr/0002-ship-as-a-claude-code-plugin.mdSource checked 2026-09-08