Skip to content
SkillModel-led1,796 tokens in use

setup-matt-pocock-skills

Configure a repo once for the engineering skills: issue tracker, triage labels and domain doc layout.

328,764 stars on the repository MIT Licensemattpocock/skills · skills/engineering/setup-matt-pocock-skills
claude plugin install mattpocock-skills@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing setup-matt-pocock-skills costs

44tokens idle
1,796tokens in use
5,408tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts and code blocks. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure17/25
  • Examples6/15
  • Output15/15
  • Size10/15
  • Resources12/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community56
  • Maturity32
  • Momentum40

Setup Matt Pocock Skills explores the current repo, presents what it found, and asks a short series of questions: which issue tracker to use, whether to keep the default triage labels, and how domain docs are laid out. It then writes an Agent skills block into CLAUDE.md or AGENTS.md and seeds docs/agents files.

Run it once per repository before using to-spec, to-tickets or triage.

What You Get

  • An Agent skills block in CLAUDE.md or AGENTS.md
  • A docs/agents/issue-tracker.md describing where issues live
  • A docs/agents/domain.md with the glossary and ADR layout
  • A docs/agents/triage-labels.md when triage is installed, with the labels created on the tracker

Common Use Cases

  • Prepare a new repo for to-spec, to-tickets and triage
  • Switch a project from GitHub issues to local markdown tickets
  • Map existing label names such as bug:triage onto the five triage roles

What Makes It Unique

It is the one setup step that the whole engineering skill set depends on, and it keeps choices small: it leads each question with a recommended answer, skips sections that exploration already settled, and defaults to a single-context domain layout unless it detects a monorepo.

Under The Hood

A SKILL.md with seed template files beside it for the GitHub, GitLab and local trackers, triage labels and domain docs. It reads git remotes, CLAUDE.md, AGENTS.md, glossary and ADR folders, then after your confirmation it edits the agent file, writes docs, and runs gh or glab label create for missing labels. It can also run git init and git remote add when you pick a tracker the repo lacks a remote for.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers