stevesolun/ctx / .agents/skills/setup-matt-pocock-skills
setup-matt-pocock-skills
VerifiedConfigure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.5 KB |
| agents/openai.yaml | config | 152 B |
| domain.md | markdown | 2.0 KB |
| issue-tracker-github.md | markdown | 3.7 KB |
| issue-tracker-gitlab.md | markdown | 3.7 KB |
| issue-tracker-local.md | markdown | 1.8 KB |
| triage-labels.md | markdown | 1.0 KB |
SKILL.md
View on GitHub---
name: setup-matt-pocock-skills
description: Configure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.
---
# Configure the repository
1. Inspect existing tracker conventions, remotes, domain documents, ADRs, and
skill configuration. Reuse established structure.
2. Determine which configuration the installed workflows actually need:
issue-tracker guidance, triage labels, domain-document guidance, or a subset.
3. Infer unambiguous choices from the repository. Ask only about choices that
materially change behavior, and present a recommendation with the tradeoff.
4. Show the proposed repository-local files before writing when the choice is
material or the files already contain user decisions.
5. Write the smallest idempotent configuration that satisfies the selected
workflows. Do not add skill inventories or workflow prose to `AGENTS.md` or
`CLAUDE.md`; keep those files lightweight and point workflows at dedicated
configuration instead.
6. Report what was configured and what remains intentionally unconfigured.
Use the existing seed files only for the selected branch:
- GitHub: [issue-tracker-github.md](issue-tracker-github.md)
- GitLab: [issue-tracker-gitlab.md](issue-tracker-gitlab.md)
- Local Markdown: [issue-tracker-local.md](issue-tracker-local.md)
- Triage labels: [triage-labels.md](triage-labels.md)
- Domain documents: [domain.md](domain.md)
Adapt templates to the repository; they are references, not required output
shapes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |