setup-matt-pocock-skills

Configure per-repo engineering skill settings for issue tracking, triage labels, and docs layout.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill setup-matt-pocock-skills-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.claude/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill setup-matt-pocock-skills-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill scaffolds the per-repo configuration that other engineering skills depend on, so they correctly discover where issues live, how triage labels are named, and where domain documentation and ADRs are stored.

Core Features & Use Cases

  • Issue tracker setup: Records whether issues are managed via GitHub, GitLab, or local markdown so downstream skills can create, read, and comment consistently.
  • Triage label vocabulary mapping: Establishes the five canonical triage roles and the exact label strings used in this repo to avoid duplicates and mis-triage.
  • Domain docs consumption rules: Documents whether the repo uses a single CONTEXT.md or a multi-context CONTEXT-MAP.md layout, plus where ADRs should be read.

Quick Start

Run the setup-matt-pocock-skills skill and answer the three configuration choices (issue tracker, triage label vocabulary, and domain docs layout) one section at a time.

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 configure AGENTS.md for repo issue tracking and domain documentation?

To configure AGENTS.md for repo issue tracking, you explore existing repo files and define issue tracker location, triage label vocabulary, and domain docs layout. This setup writes or updates AGENTS.md and docs/agents/*.md files using provided templates.

When do I need to set up per-repo configuration for engineering skills?

You need per-repo configuration before first using skills like to-issues, triage, diagnose, or tdd, or when expected context appears missing. It ensures downstream engineering skills correctly discover issue locations and domain documentation.

What's the best way to establish triage label vocabulary in a Git repository?

Establishing triage label vocabulary involves mapping five canonical triage roles to exact label strings used in your repo. This prevents duplicate labels and mis-triage by recording the vocabulary in AGENTS.md during setup.

Does this repo configuration support both GitHub and GitLab issue trackers?

Yes, repo configuration supports GitHub, GitLab, and local markdown issue trackers. You select your tracker during setup so downstream skills can consistently create, read, and comment on issues in the correct platform.

How do I document domain docs layout and ADR structure for my codebase?

Documenting domain docs layout involves choosing between a single CONTEXT.md or multi-context CONTEXT-MAP.md structure. The configuration process records this choice and specifies where Architecture Decision Records should be read.

Why does my triage or diagnose skill fail to find expected repo context?

Skills fail to find expected repo context when AGENTS.md is missing or unconfigured. Running the setup skill explores existing files and writes the required configuration so downstream skills can locate issue trackers and domain docs.