setup-matt-pocock-skills

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

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

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 apply, and where domain documentation resides. Without per-repo configuration, these skills guess at conventions and produce inconsistent results. This skill scaffolds that configuration once, before first use. ## Core Features & Use Cases - Issue tracker setup: Records whether issues live in GitHub (gh CLI), GitLab (glab CLI), local markdown under .scratch/, or another 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 repo's actual label strings. - Domain doc layout: Configures single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts and consumer rules. - Use Case: After installing the engineering skills into a GitHub repo, run this setup once to generate docs/agents/*.md files and an Agent skills block in CLAUDE.md or AGENTS.md so every other skill reads consistent conventions. ## 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.

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 Matt Pocock's engineering skills?▼

Run the setup-matt-pocock-skills skill once before using the other skills. It explores your repo, asks about your issue tracker, triage labels, and domain docs, then writes configuration files under docs/agents/ and updates 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/<feature>/. 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 your git remote points at GitLab, the skill proposes GitLab and writes docs/agents/issue-tracker.md from the GitLab seed template, using glab CLI commands for creating, reading, labeling, and closing issues.

What are the default triage labels used by the triage skill?▼

The five canonical labels are needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. The setup skill writes these as-is by default, or records your custom label strings if your tracker already uses different names.

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

Multi-context layout with a root CONTEXT-MAP.md and per-context CONTEXT.md files is only offered when the repo shows monorepo signals like pnpm-workspace.yaml or a workspaces field. Single-context with one CONTEXT.md and docs/adr/ fits almost every repo.

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.