Agent skill

Setup Matt Pocock Skills

Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…

MITAuto-check passedAgent Workflows

Install Setup Matt Pocock Skills

skills CLI

$ npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install yamcodes/arkenv setup-matt-pocock-skills --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/setup-matt-pocock-skills .claude/skills/setup-matt-pocock-skills && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "setup-matt-pocock-skills" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills into .claude/skills/setup-matt-pocock-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-matt-pocock-skills", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install yamcodes/arkenv setup-matt-pocock-skills --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/setup-matt-pocock-skills .agents/skills/setup-matt-pocock-skills && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "setup-matt-pocock-skills" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills into .agents/skills/setup-matt-pocock-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-matt-pocock-skills", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install yamcodes/arkenv setup-matt-pocock-skills --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/setup-matt-pocock-skills .cursor/skills/setup-matt-pocock-skills && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "setup-matt-pocock-skills" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills into .cursor/skills/setup-matt-pocock-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-matt-pocock-skills", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/yamcodes/arkenv.git --path skills/setup-matt-pocock-skills

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install yamcodes/arkenv setup-matt-pocock-skills --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/setup-matt-pocock-skills .gemini/skills/setup-matt-pocock-skills && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "setup-matt-pocock-skills" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills into .gemini/skills/setup-matt-pocock-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-matt-pocock-skills", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install yamcodes/arkenv setup-matt-pocock-skills

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/setup-matt-pocock-skills .github/skills/setup-matt-pocock-skills && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "setup-matt-pocock-skills" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills into .github/skills/setup-matt-pocock-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-matt-pocock-skills", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install yamcodes/arkenv setup-matt-pocock-skills --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/setup-matt-pocock-skills .opencode/skills/setup-matt-pocock-skills && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "setup-matt-pocock-skills" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/setup-matt-pocock-skills into .opencode/skills/setup-matt-pocock-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-matt-pocock-skills", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: setup-matt-pocock-skills
GitHub stars: 147
Token cost: ~1.8k tokens
SKILL.md length: 873 words
Files: 6
Skills in repo: 21
Repo updated: Oct 10, 2026
First seen: Oct 10, 2026
Licence: MIT

At a glance

Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…

Works in 5 steps: Explore → Present findings and ask → Confirm and edit → …
Tasks that involve Issue triage
Calls git and gh
Tasks that involve Agent instruction files

What it does

Setup Matt Pocock Skills is an agent skill from yamcodes/arkenv. Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of to-issues, to-prd, triage, diagnose, tdd, improve-codebase-architecture, or zoom-out - or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `domain.md`, `issue-tracker-github.md` and `issue-tracker-gitlab.md`).

It sits in Agent Workflows, covering Issue triage, Agent instruction files and PRD writing. It works with GitHub and Git. The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.

When your agent uses it

Tasks that involve Issue triage
Tasks that involve Agent instruction files
Tasks that involve PRD writing

Example prompts

“/setup-matt-pocock-skills”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Explore
Present findings and ask
Confirm and edit
Write
Done

What it can do on your machine

Read from SKILL.md and the folder at commit 1e47aed. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- gitlab.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Setup Matt Pocock Skills loads about 1.8k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 873 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~116
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yamcodes/arkenv at commit 1e47aed, republished under its MIT licence (© yamcodes). 873 words, ~1,759 tokens.

Download SKILL.mdSave it as .claude/skills/setup-matt-pocock-skills/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: setup-matt-pocock-skills
description: Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `.agent/docs/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` - or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
disable-model-invocation: true
metadata.internal: true

Setup matt pocock's skills

Scaffold the per-repo configuration that the engineering skills assume:

Issue tracker - where issues live (GitHub by default; local markdown is also supported out of the box)
Triage labels - the strings used for the six canonical triage roles
Domain docs - where docs/CONTEXT.md and ADRs live, and the consumer rules for reading them

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.

Process

1. Explore

Look at the current repo to understand its starting state. Read whatever exists; don't assume:

git remote -v and .git/config - is this a GitHub repo? Which one?
AGENTS.md and CLAUDE.md at the repo root - does either exist? Is there already an ## Agent skills section in either?
docs/CONTEXT.md and CONTEXT-MAP.md (at the repo root)
docs/adr/ and any src/*/docs/adr/ directories
.agent/docs/ - does this skill's prior output already exist?
.scratch/ - sign that a local-markdown issue tracker convention is already in use

2. Present findings and ask

Summarise what's present and what's missing. Then walk the user through the three decisions one at a time - present a section, get the user's answer, then move to the next. Don't dump all three at once.

Assume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.

Section A - Issue tracker.

Explainer: The "issue tracker" is where issues live for this repo. Skills like to-issues, triage, to-prd, and qa read from and write to it - they need to know whether to call gh issue create, write a markdown file under .scratch/, or follow some other workflow you describe. Pick the place you actually track work for this repo.

Default posture: these skills were designed for GitHub. If a git remote points at GitHub, propose that. If a git remote points at GitLab (gitlab.com or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:

GitHub - issues live in the repo's GitHub Issues (uses the gh CLI)
GitLab - issues live in the repo's GitLab Issues (uses the glab CLI)
Local markdown - issues live as files under .scratch/<feature>/ in this repo (good for solo projects or repos without a remote)
Other (Jira, Linear, etc.) - ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose

Section B - Triage label vocabulary.

Explainer: When the triage skill processes an incoming issue, it moves it through a state machine - needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, blocked on an external dependency, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings you've actually configured. If your repo already uses different label names (e.g. bug:triage instead of needs-triage), map them here so the skill applies the right ones instead of creating duplicates.

The six canonical roles:

needs-triage - maintainer needs to evaluate
needs-info - waiting on reporter
ready-for-agent - fully specified, ready for immediate implementation (pick it up yourself or with an agent)
ready-for-human - needs a judgment call or design decision before implementation
blocked - specified, but work cannot start until an external dependency clears. Mutually exclusive with the ready roles
wontfix - will not be actioned

Show full SKILL.md (319 more words)Show less

Default: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.

Section C - Domain docs.

Explainer: Some skills (improve-codebase-architecture, diagnose, tdd) read a docs/CONTEXT.md file to learn the project's domain language, and docs/adr/ for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend/backend contexts) so they look in the right place.

Confirm the layout:

Single-context - one docs/CONTEXT.md + docs/adr/. Most repos are this.
Multi-context - CONTEXT-MAP.md at the root pointing to per-context CONTEXT.md files (typically a monorepo).

3. Confirm and edit

Show the user a draft of:

The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)
The contents of .agent/docs/issue-tracker.md, .agent/docs/triage-labels.md, .agent/docs/domain.md

Let them edit before writing.

4. Write

Pick the file to edit:

If CLAUDE.md exists, edit it.
Else if AGENTS.md exists, edit it.
If neither exists, ask the user which one to create - don't pick for them.

Never create AGENTS.md when CLAUDE.md already exists (or vice versa) - always edit the one that's already there.

If an ## Agent skills block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.

The block:

markdown

## Agent skills

### Issue tracker

[one-line summary of where issues are tracked]. See `.agent/docs/issue-tracker.md`.

### Triage labels

[one-line summary of the label vocabulary]. See `.agent/docs/triage-labels.md`.

### Domain docs

[one-line summary of layout - "single-context" or "multi-context"]. See `.agent/docs/domain.md`.

Then write the three docs files using the seed templates in this skill folder as a starting point:

issue-tracker-github.md - GitHub issue tracker
issue-tracker-gitlab.md - GitLab issue tracker
issue-tracker-local.md - local-markdown issue tracker
triage-labels.md - label mapping
domain.md - domain doc consumer rules + layout

For "other" issue trackers, write .agent/docs/issue-tracker.md from scratch using the user's description.

5. Done

Tell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit .agent/docs/*.md directly later - re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.

Files

SKILL.md and 5 other files in skills/setup-matt-pocock-skills of yamcodes/arkenv.

SKILL.md
domain.md
issue-tracker-github.md
issue-tracker-gitlab.md
issue-tracker-local.md
triage-labels.md

Open the folder on GitHubat commit 1e47aed

Compare with similar skills

Setup Matt Pocock Skills next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Setup Matt Pocock Skills compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Setup Matt Pocock Skills this skillyamcodes/arkenv	147	—	~1.8k	Automated safety check: Pass	MIT	today
Setup Matt Pocock Skillsywwynm/EverythingDone	144	8 repos	~1.7k	Automated safety check: Pass	GPL-3.0	yesterday
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Ad ReviewCorridorTech/PoseCap	224	—	~2.4k	Automated safety check: Notes	Apache-2.0	3 days ago
Project Context SetupMathews-Tom/armory	329	—	~1.2k	Automated safety check: Pass	MIT	4 days ago
Audit Standardsjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.8k	Automated safety check: Notes	MIT	today

Similar skills

Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
144 GitHub starsUsed in 8 repos~1.7k tokens
Agent WorkflowsAuto-check passed
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Ad Review
CorridorTech/PoseCap
Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.
224 GitHub stars~2.4k tokensUpdated 3 days ago
DevelopmentAuto-check: notes
Project Context Setup
Mathews-Tom/armory
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions.
329 GitHub stars~1.2k tokensUpdated 4 days ago
Agent WorkflowsAuto-check passed
Audit Standards
jeremylongshore/tons-of-skills-marketplace
Audits the current project against the development standards defined in ~/.claude/CLAUDE.md.
2.8k GitHub stars~1.8k tokensUpdated today
Agent WorkflowsAuto-check: notes
Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
458 GitHub stars~1.3k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check: notes

Questions about Setup Matt Pocock Skills

What does Setup Matt Pocock Skills do?

Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…. Setup Matt Pocock Skills is an agent skill from yamcodes/arkenv.agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout.

When should I use Setup Matt Pocock Skills?

Setup Matt Pocock Skills fits situations like: tasks that involve Issue triage; tasks that involve Agent instruction files; tasks that involve PRD writing.

How do I install Setup Matt Pocock Skills in Claude Code?

Run `npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a claude-code`. Or copy the skill folder (skills/setup-matt-pocock-skills in yamcodes/arkenv) into .claude/skills/setup-matt-pocock-skills in your project. Claude Code loads it when a task matches its description.

How do I install Setup Matt Pocock Skills in Codex?

Run `npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a codex`. Or copy the skill folder (skills/setup-matt-pocock-skills in yamcodes/arkenv) into .agents/skills/setup-matt-pocock-skills in your project. Codex loads it when a task matches its description.

Can I use Setup Matt Pocock Skills in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yamcodes/arkenv --skill setup-matt-pocock-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup-matt-pocock-skills, .gemini/skills/setup-matt-pocock-skills, .github/skills/setup-matt-pocock-skills and .opencode/skills/setup-matt-pocock-skills in your project.

What does Setup Matt Pocock Skills need to run?

Going by SKILL.md and its folder, Setup Matt Pocock Skills needs the command-line tools its instructions call (git and gh).

Does Setup Matt Pocock Skills access the network?

SKILL.md names 1 domain. As links in the text: gitlab.com. This is read from the text; nothing was executed.

Is Setup Matt Pocock Skills safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Setup Matt Pocock Skills use?

Setup Matt Pocock Skills is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Setup Matt Pocock Skills use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Setup Matt Pocock Skills?

Skills that share tags, products or a category with Setup Matt Pocock Skills: Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Ad Review (CorridorTech/PoseCap, 224 stars) and Project Context Setup (Mathews-Tom/armory, 329 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setup Matt Pocock Skills?

yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 147 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.

Source: yamcodes/arkenv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Setup Matt Pocock Skills

Install Setup Matt Pocock Skills

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Setup matt pocock's skills

Process

1. Explore

2. Present findings and ask

3. Confirm and edit

4. Write

5. Done

Files

Compare with similar skills

Similar skills