setup-matt-pocock-skills

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/mikalv/pi-extensions --skill setup-matt-pocock-skills-mikalv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/mikalv/pi-extensions/tree/main/packages/pi-atelier/.agents/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/mikalv/pi-extensions --skill setup-matt-pocock-skills-mikalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, to-tickets, and wayfinder need to know where issues live, which label vocabulary to use, and where domain docs reside — but every repo answers these differently. This Skill scaffolds that per-repo configuration once, so the other skills work without repeated explanation. ## Core Features & Use Cases - Issue tracker setup: Detects GitHub or GitLab remotes and records the chosen tracker (GitHub, GitLab, local markdown under .scratch/, or a custom workflow) in docs/agents/issue-tracker.md. - Triage label vocabulary: Writes the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or custom overrides to docs/agents/triage-labels.md. - Domain doc layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md for monorepos) layout in docs/agents/domain.md, and adds an ## Agent skills block to the existing CLAUDE.md or AGENTS.md. - Use Case: After installing the engineering skills into a GitHub repo, run this once to generate the docs/agents/ configuration files so triage and to-tickets immediately know to use gh CLI commands and the default 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.

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 tracking for AI engineering skills in a repo?▼

Run this setup skill once in the repo. It explores your git remote and existing docs, asks which tracker you use (GitHub, GitLab, local markdown, or other), then writes the choice to docs/agents/issue-tracker.md for other skills to read.

What triage labels does the setup configure?▼

It configures five canonical labels: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. If your tracker already uses different names, you can provide overrides and the mapping is recorded in docs/agents/triage-labels.md.

Does this skill work with GitLab or only GitHub?▼

It supports GitHub, GitLab, and local markdown trackers out of the box. GitHub uses the gh CLI, GitLab uses the glab CLI, and local markdown stores issues as files under .scratch/<feature>/. Other trackers like Jira can be recorded as freeform prose.

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

Single-context (one CONTEXT.md plus docs/adr/ at the root) fits almost every repo and is the default. Multi-context with a CONTEXT-MAP.md pointing to per-package CONTEXT.md files is only offered when monorepo signals like pnpm-workspace.yaml or a workspaces field are detected.

What happens if neither CLAUDE.md nor AGENTS.md exists?▼

The skill asks you which file to create rather than choosing for you. If one already exists, it edits that file and never creates the other, updating any existing Agent skills section in place instead of duplicating it.