# Setup Matt Pocock Skills

Configure this repo for the engineering skills, set up its issue tracker, triage label...

- Repository: https://github.com/rpamis/comet (3263 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rpamis/comet --skill setup-matt-pocock-skills -g -a claude-code -y`
Codex: `npx skills add rpamis/comet --skill setup-matt-pocock-skills -g -a codex -y`
Cursor: `npx skills add rpamis/comet --skill setup-matt-pocock-skills -g -a cursor -y`
Gemini CLI: `npx skills add rpamis/comet --skill setup-matt-pocock-skills -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Setup Matt Pocock's Skills

Scaffold the per-repo configuration that the engineering skills assume:

- **Issue tracker**, where issues live (GitHub by default; local markdown is also supported out of the box)
- **Triage labels**, the strings used for the five canonical triage roles
- **Domain docs**, where `CONTEXT.md` and ADRs live, and the consumer rules for reading them

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.

## Process

### 1. Explore

Look at the current repo to understand its starting state. Read whatever exists; don't assume:

- `git remote -v` and `.git/config`, is this a GitHub repo? Which one?
- `AGENTS.md` and `CLAUDE.md` at the repo root, does either exist? Is there already an `## Agent skills` section in either?
- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root
- `docs/adr/` and any `src/*/docs/adr/` directories
- `docs/agents/`, does this skill's prior output already exist?
- `.scratch/`, sign that a local-markdown issue tracker convention is already in use
- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.
- Monorepo signals, a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages/*` with its own `src/`. Present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.

### 2. Present findings and ask

Summarise what's present and what's missing. Then take the sections in order, one section, one answer, then the next.

Lead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).

**Section A, Issue

The rest: https://github.com/rpamis/comet/blob/HEAD/eval/archives/grill-test-20261013/application/skills/setup-matt-pocock-skills/SKILL.md