setup-matt-pocock-skills

Configure a repository's issue tracker, triage labels, and domain doc layout for engineering skills.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/yamcodes/the-hat --skill setup-matt-pocock-skills-yamcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/yamcodes/the-hat/tree/main/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/yamcodes/the-hat --skill setup-matt-pocock-skills-yamcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where issues live, which label vocabulary to apply, and where domain documentation resides. Without a one-time per-repo configuration, each skill would guess at these conventions and produce inconsistent results. ## Core Features & Use Cases - Issue Tracker Setup: Detects the repo's remote and records whether issues live in GitHub (gh CLI), GitLab (glab CLI), local markdown under .scratch/, or another tracker described in freeform prose. - Triage Label Vocabulary: Maps the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to the label strings actually used in the repo's tracker. - Domain Doc Layout: Records single-context (one CONTEXT.md plus docs/adr/) or multi-context (CONTEXT-MAP.md with per-context files) documentation structure and consumer rules. - Use Case: After installing the engineering skills in a GitHub repo, run this setup once to write docs/agents/issue-tracker.md, docs/agents/triage-labels.md, and docs/agents/domain.md, plus an Agent skills block in CLAUDE.md or AGENTS.md, so every other skill reads consistent conventions. ## Quick Start Ask the AI assistant to run the setup skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.

Frequently Asked Questions about setup-matt-pocock-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up issue tracker configuration for AI engineering skills?▼

Run the setup skill once in the repo. It explores your git remote and existing files, asks which tracker you use (GitHub, GitLab, local markdown, or other), then writes docs/agents/issue-tracker.md and updates CLAUDE.md or AGENTS.md with an Agent skills block.

What triage labels does the setup skill configure?▼

It configures five canonical triage roles: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. The defaults use label strings equal to the role names, but you can override them to match labels your tracker already uses.

Does the setup skill support GitLab or only GitHub?▼

It supports GitHub via the gh CLI, GitLab via the glab CLI, and local markdown files under .scratch/. Other trackers like Jira or Linear can be recorded as freeform prose describing your workflow.

When should I use multi-context domain docs instead of single-context?▼

Use multi-context only when the repo shows monorepo signals such as pnpm-workspace.yaml, a workspaces field in package.json, or populated packages with their own src directories. Almost every repo fits the single-context default of one CONTEXT.md plus docs/adr/ at the root.

Do I need to re-run the setup skill after editing the config files?▼

No. You can edit docs/agents/*.md directly at any time. Re-running the skill is only necessary if you want to switch issue trackers or restart the configuration from scratch.