What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where issues live, which label vocabulary to use, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so every other engineering skill reads from consistent, well-defined files instead of guessing. ## Core Features & Use Cases - Issue tracker setup: Detects the repo's remote and records whether issues live in GitHub, GitLab, local markdown under .scratch/, or a custom tracker, writing the choice to docs/agents/issue-tracker.md. - 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 whether the repo uses a single-context layout (CONTEXT.md + docs/adr/) or a multi-context layout with CONTEXT-MAP.md for monorepos. - Use Case: After installing the engineering skills into a GitHub repo, run this Skill once to generate docs/agents/ config files and an ## Agent skills block in CLAUDE.md, so subsequent triage and ticket workflows operate against GitHub Issues with the correct labels. ## Quick Start Ask the agent to run the setup-matt-pocock-skills skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.