floatboat
Open navigation menu

Setup Matt Pocock Skills

Set up the repository context that Matt Pocock’s engineering Skills use to find issues, apply triage labels and read domain decisions.

Review one repository’s engineering Skill setup

Use the current repository conventions to propose tracker, label and domain-document configuration for review.

Include the current tracker, existing labels and glossary or ADR locations.

Copy the request into a new Floatboat conversation and provide the required material.

Download Floatboat

Your request for Floatboat

Preview and copy the request. It is not sent automatically from this page.

Reference: Setup Matt Pocock Skills
https://github.com/mattpocock/skills/blob/main/skills/engineering/setup-matt-pocock-skills/SKILL.md

Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding.

My task:
Use Setup Matt Pocock Skills to inspect our existing issue tracker and glossary. Show the proposed docs/agents/ configuration and any label changes. Wait before writing files or changing the tracker.

Expected deliverable:
A configuration draft with proposed file paths and any remote changes separated for approval.

What Setup Matt Pocock Skills does

Setup explores the repository, proposes an issue tracker and domain-document layout, and maps triage roles when Triage is installed. It drafts a root agent-instructions section and reference files under docs/agents/ for review before writing. The resulting files are shared configuration for downstream Skills such as Triage.

Setup Matt Pocock Skills use cases

The configuration is ready when a downstream Skill can find the intended issue and the right domain docs. Use one existing issue and one decision record to check both paths.

Keep an established tracker

When a repository already uses GitHub or GitLab, inspect its remote and current issue workflow. Confirm which repository should receive updates so an agent does not write to a fork.

Reuse an existing label vocabulary

If the team already uses custom triage names, map the five roles to those exact strings. Check a sample issue and avoid creating a parallel set of labels.

Set up a local backlog

For a solo repository, select local Markdown and write down where issues are stored. Check that a new agent session can find one issue without assuming a hosted tracker.

Locate domain docs in a monorepo

Identify which packages have separate domain language or decisions, then review a glossary map that points agents to the correct documentation for each area.

How to use Setup Matt Pocock Skills

Inspect the repository’s existing tracker and domain docs before drafting configuration. Review the exact root instruction block, files under docs/agents/ and any labels that would change upstream.

  1. Inspect the repository

    Read its remotes, root agent instructions, existing tracker files and glossary before proposing any new structure.

  2. Review the configuration draft

    Confirm the tracker and domain layout. If Triage is installed, verify the role-to-label mapping and any remote changes.

  3. Write and spot-check

    After approval, write the configuration and have a downstream Skill identify the intended tracker and docs from it.

Explore More Agent Skills

Read another Skill guide and check its original source before using it.

Setup Matt Pocock Skills FAQ

When should I run Setup?
Run it before first using engineering Skills that depend on repository-specific tracker, label or domain-document settings.
Does this install the other Skills?
Setup itself configures the current repository. Install the individual downstream Skills or bundle through its documented installation route.
Can I use a local issue tracker?
Yes. Local Markdown is a documented choice. The setup records the location and conventions instead of assuming GitHub.
Does it always configure triage labels?
That section depends on whether Triage is present. If it is installed, confirm whether to keep the defaults or map existing labels.
What should I review before applying it?
Read the proposed Agent skills block, docs/agents/ references and any remote label changes against your current repository conventions.
Do I need a glossary map?
Most repositories use one glossary. A multi-context map is useful when different packages have distinct vocabulary and decisions.