setup-matt-pocock-skills

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

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

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 use, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so every other engineering skill reads consistent settings instead of guessing. ## 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 a custom tracker, written 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 repo's actual label strings in docs/agents/triage-labels.md. - Domain doc layout: Records single-context or multi-context layout for CONTEXT.md and ADR files in docs/agents/domain.md, and adds an Agent skills block to CLAUDE.md or AGENTS.md. - Use Case: After installing a set of engineering skills in a GitHub repo, run this once to generate the docs/agents/ configuration files so triage and ticketing skills operate against GitHub Issues with the correct labels. ## Quick Start Ask the agent 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 configure a repo for engineering skills like triage and to-tickets?▼

Run this setup skill once per repo. It explores your git remote and existing docs, asks which issue tracker you use, then writes docs/agents/issue-tracker.md, triage-labels.md, and domain.md plus an Agent skills block in CLAUDE.md or AGENTS.md.

Which issue trackers does the setup skill support?▼

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

Does the setup skill work with GitLab instead of GitHub?▼

Yes. If the git remote points at GitLab, the skill proposes GitLab and writes a tracker doc using glab CLI conventions, including merge request handling and native blocking links via the /blocked_by quick action.

What are the default triage labels the skill configures?▼

The five canonical labels are needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. If your tracker already uses different names, you can provide overrides so the triage skill applies your existing labels instead of creating duplicates.

When should I re-run the setup skill?▼

Re-running is only necessary if you want to switch issue trackers or restart the configuration from scratch. For smaller changes, you can edit the files under docs/agents/ directly at any time.