setup-matt-pocock-skills

Configures issue tracker, triage labels, and domain doc layout for engineering skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, to-issues, and qa need to know where issues live, which label vocabulary to apply, and where domain documentation resides. This Skill scaffolds that per-repo configuration once so the other skills read consistent settings instead of guessing. ## Core Features & Use Cases - Issue tracker setup: Detects GitHub or GitLab remotes and records the tracker workflow (gh CLI, glab CLI, local markdown under .scratch/, or a custom freeform description) in docs/agents/issue-tracker.md. - Triage label mapping: 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. - Domain doc layout: Records whether the repo uses a single CONTEXT.md or a multi-context CONTEXT-MAP.md with per-context ADR directories. - Use Case: After cloning a repo that will use the engineering skills, run this setup once to generate docs/agents/*.md files and an Agent skills section in CLAUDE.md or AGENTS.md. ## Quick Start Ask the assistant to run the setup skill to configure the issue tracker, triage labels, and domain docs for this repository.

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 an issue tracker for Claude engineering skills?▼

Run this setup skill once in the repo. It inspects git remotes to detect GitHub or GitLab, then writes docs/agents/issue-tracker.md describing the workflow using the gh or glab CLI, or local markdown files under .scratch/.

What triage labels does the setup skill configure?▼

It maps five canonical roles: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. Each role defaults to its own name, but you can override the strings to match labels your tracker already uses.

Does the setup skill support GitLab or only GitHub?▼

Yes, it supports GitLab via the glab CLI in addition to GitHub via gh. It also supports local markdown issue tracking under .scratch/ and freeform descriptions for other trackers like Jira or Linear.

When should I re-run the repo setup skill?▼

Re-run it only when switching issue trackers or restarting configuration from scratch. For ordinary changes, edit the generated docs/agents/*.md files directly instead of re-running the skill.

What is the difference between single-context and multi-context domain docs?▼

Single-context repos have one CONTEXT.md and docs/adr/ at the root. Multi-context repos, typically monorepos, use a CONTEXT-MAP.md at the root pointing to per-context CONTEXT.md files and context-scoped ADR directories.