Matt Pocock skills
Installing Matt Pocock skills: managed plugin or editable files?
Choose a distribution model, verify the installed revision and avoid using the repository maintainer’s destructive linking script as a general installer.
What you will learn
- Choose ownership before choosing a command
- Do not confuse a release with an installed update
- Treat local linking as a maintainer operation
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
- Managed updates and editable copies have different ownership costs.
- Record the installed revision, not only a version label or repository tag.
- The development linking script is not the general installation path.
Choose ownership before choosing a command
The pinned README documents two distribution approaches. A Claude Code plugin delivers a managed bundle, while the skills.sh route copies editable skill files for supported hosts. The central tradeoff is ownership: do you want to follow upstream’s curated set, or maintain adaptations in your project? Installing both can create duplicate skill names and confusing provenance.
The commands below reproduce the repository’s documented entry points as alternatives, not a sequence to run together. They were not executed in this review. A latest-tag installer is not revision-pinned; inspect the selected package, requested permissions and resulting file changes before accepting it in a production repository.
Do not confuse a release with an installed update
The package and plugin version fields both read 1.2.3 in the inspected source. The distribution ADR explains that the official marketplace entry used a pinned source revision: a repository tag alone did not make every subscriber receive that revision. Its installation observations are dated August 5, 2026, not a current installation test performed by this review.
Capture the host version, installation method, resolved repository revision and actual skill inventory after an installation. Compare those observations with the manifest you intended to use. A mismatch can be a distribution delay or a different selected source; repeatedly reinstalling without recording the resolved revision makes that diagnosis harder.
Treat local linking as a maintainer operation
scripts/link-skills.sh explicitly identifies itself as development-only. It targets the user-level Claude and agent skill directories, creates links back to this checkout and includes in-progress skills while excluding miscellaneous and deprecated buckets. Its set therefore differs from the promoted plugin manifest. A pull in the linked checkout also changes the linked instructions.
More importantly, an existing same-name non-symlink target is recursively removed before linking. The script contains a guard against a destination symlink pointing back into the repository, but that guard is not a backup policy for existing installed directories. This review did not run it. Use the documented distribution route and preserve local customizations instead of treating a maintainer convenience as a safe universal installer.
Implementation steps
- 1
Choose exactly one documented distribution approach.
- 2
Inspect the target host and existing same-name skills.
- 3
Review installation changes and record the resolved revision.
- 4
Run repository setup only after inspecting the selected skills.
Copy-ready example
Documented alternatives; not executed in this review:
Managed Claude Code plugin:
claude plugins install mattpocock-skills
Editable skill files:
npx skills@latest add mattpocock/skills
Choose one route. Inspect changes before adopting them.Frequently asked questions
Should I run link-skills.sh for a quick installation?
It is a maintainer development tool and can delete same-name non-symlink targets. This series does not recommend it as a general installer.
Does a new Git tag prove my managed installation is current?
No. Check the source revision and inventory actually resolved by the distribution channel.
Sources
- README.mdSource checked 2026-09-08
- package.jsonSource checked 2026-09-08
- .claude-plugin/plugin.jsonSource checked 2026-09-08
- scripts/link-skills.shSource checked 2026-09-08
- .agents/adr/0002-ship-as-a-claude-code-plugin.mdSource checked 2026-09-08