Manage skills

Add a skill

Add it to the stack, then review and apply as usual:

pegboard add skill mattpocock/skills@tdd
pegboard plan
pegboard apply

You can also list skills directly in pegboard.yaml:

skills:
  - mattpocock/skills@tdd
  - vercel-labs/agent-skills
  - github.com/anthropics/skills//skills/pdf?ref=main
  - ./skills/my-skill
  - pegboard
  - source: ./skills/review
    agents: [codex, opencode]

Sources

Pegboard uses the same source conventions as npx skills and skills.sh, so any skills repo works with both.

Source	What you get
owner/repo	All skills in a GitHub repo
owner/repo@skill	One skill from the repo
github.com/owner/repo//path	A subdirectory, on any git host
https://github.com/o/r/tree/<ref>/<path>	A GitHub or GitLab URL
https://…, git@…	Any git repo, with optional //path
./path, ~/path, /path	A local skill, linked as-is
pegboard	The built-in skill

Git sources accept ?ref=<branch|tag|commit>. They download with your system git, so credentials you already have for private repos will work.

How they’re installed

Each skill is downloaded once to ~/.cache/pegboard and linked into every agent’s skills directory. It’s copied instead if the agent doesn’t follow symlinks, or on Windows. Either way, the lock guarantees that every agent gets the same content.

Update skills

pegboard update
pegboard update mattpocock/skills@tdd

update resolves new versions, shows you the diff, and rewrites pegboard.lock. Third-party skills are third-party code, so it’s worth reading that diff.

Remove a skill

pegboard remove skill mattpocock/skills@tdd
pegboard plan
pegboard apply