Matt Pocock Skills: install a daily engineering skill set in Claude Code

Who it's for

Use the plugin from this repository when you want a daily agent skill set in Claude Code that is aimed at real engineering, not vibe coding. The main path is the plugin in the official marketplace, not a second unnamed installer you assemble yourself.

There are two preconditions. First, the current environment is Claude Code, and you accept the official marketplace: the notes say it is already in Claude Code's official marketplace, you do not need to add another source first, and updates arrive automatically. Second, you may pick only one install path — “Pick one: installing both leaves you with every skill twice.” Do not install two copies at the same time.

The notes do not write this set as the official install method for other agents. Do not transplant the marketplace plugin command onto unnamed platforms, and do not invent a directory that never appears as the skill source.

First try in 3 minutes

Official page:

https://github.com/mattpocock/skills

The recommended install is this one path only. Confirm you are in Claude Code, and that this pass installs only the plugin and does not install a second copy in parallel, then run:

claude plugins install mattpocock-skills

This command changes local plugin state. Read the line above before you run it. After it runs, return to the Claude Code plugin list and confirm mattpocock-skills is there. If the command fails or the name is missing from the list, stop. Do not switch to an installer that never appears.

The first pass should not “run it once per repo” on a production repository. In Claude Code, only confirm the plugin is installed and that you can see skill names. Success signals: the plugin list shows mattpocock-skills, and you did not also install a second copy.

If you later enable it for a repository, pick a disposable repo first, then run it once for that repo in the agent. The notes only write “In your agent, run it once per repo. It will:”; the visible text cuts off there. After the run, only check whether that repo shows new configuration changes. Do not invent a command name or a follow-up step list.

Use cases

Case 1: install only through the Claude Code official marketplace. In Claude Code, run claude plugins install mattpocock-skills. The notes stress it is already in the official marketplace, you need not add a source first, and updates arrive automatically. After install, only check that the plugin appears and that you installed this one set only. Do not promote this marketplace install to other platforms.

Case 2: run it once for a single repository. The notes write “In your agent, run it once per repo.” Pick a reversible repo, confirm the plugin is installed, then run that one time. After the run, open the repo and see whether new configuration or files appeared; only then talk about the next repo. The visible text gives no command name and does not list the items after “It will:”. Do not invent the missing parts.

Boundaries

The main path is claude plugins install mattpocock-skills, and you may pick only one install path. Installing both leaves you with every skill twice.

Official marketplace and automatic updates are evidenced only for Claude Code. Do not infer that other clients already appear the same way in an official marketplace, and do not add a source.

“Run it once per repo” is evidenced only as that sentence. Do not invent a command name, a directory, or which files it will change.

The notes give no language range, no pricing, and no operations beyond the two above. Keep unknown items unknown.