Verified:GitHub

setup-matt-pocock-skills

Standardizes repository-level agent configs for GitHub, GitLab, and local markdown environments.

113|23|Updated Mar 23, 2026

Search Tags:#workflow #documentation #scaffolding #agent #configuration #triage

One-click install

npx skills add https://github.com/opensage-agent/opensage-adk --skill setup-matt-pocock-skills-opensage-agent

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/setup-matt-pocock-skills
Command: npx skills add https://github.com/opensage-agent/opensage-adk --skill setup-matt-pocock-skills-opensage-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves configuration drift by standardizing how engineering agents interact with issue trackers, triage labels, and domain documentation across different repositories.

Core Features & Use Cases

Unified Configuration: Scaffolds the necessary files to ensure agents understand the project's issue tracker (GitHub, GitLab, or local markdown) and triage vocabulary.
Context Alignment: Sets up domain documentation structures (CONTEXT.md and ADRs) so agents can accurately interpret project-specific language and architectural decisions.
Use Case: When starting work on a new repository, use this skill to ensure that all subsequent engineering agents are aligned on how to report issues, label tasks, and read project documentation.

Quick Start

Run the setup-matt-pocock-skills skill to initialize the agent configuration and documentation structure 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 standardize agent workflows and documentation across multiple repositories?▼

Standardize agent workflows by scaffolding repository-level configuration files that define issue tracker processes, triage label vocabularies, and domain documentation layouts. This ensures consistent engineering agent behavior and eliminates configuration drift across GitHub, GitLab, and local markdown environments.

What is the best way to configure triage labels for engineering agents?▼

Configure triage labels by scaffolding a standardized vocabulary within your repository configuration files. This aligns engineering agents on task reporting and labeling conventions, ensuring consistent behavior during issue triage across different repositories.

How do I set up domain documentation structures for AI agents?▼

Set up domain documentation by scaffolding structures like CONTEXT.md and ADRs into your repository. This allows engineering agents to accurately interpret project-specific language and architectural decisions during task execution.

Does agent configuration scaffolding work with both GitHub and GitLab?▼

Yes, agent configuration scaffolding operates across GitHub, GitLab, and local markdown environments. It standardizes how engineering agents interact with issue trackers and triage labels within these platforms to maintain consistent task execution behavior.

What do I need to scaffold agent-readiness files in my repository?▼

Scaffolding agent-readiness files requires access to your repository root files and documentation directories. The setup process initializes the necessary configuration structures to ensure engineering agents understand your project's issue tracker workflows.

Why does my engineering agent misinterpret project-specific context in different repositories?▼

Engineering agents misinterpret context due to configuration drift across repositories. Standardizing domain documentation layouts with CONTEXT.md and ADRs ensures agents accurately understand project-specific language and architectural decisions during execution.