Getting Started¶

Use the repo as either a published plugin catalog or a local skills workbench.

Use A Published Skill¶

Install the catalog for your host from Install.
Pick a canonical skill ID from Skills.
Invoke the skill in your agent UI.

Common entries:

Goal	Skill
Scout a codebase	`vd:scout`
Debug a failure	`vd:debug`
Plan a multi-step change	`vd:plan`
Execute a plan	`vd:cook`
Ship a branch	`vd:ship`
Update docs	`vd:docs`

Source: skills/<name>/SKILL.md frontmatter.

Edit A Skill¶

bash scripts/new-skill.sh my-skill
$EDITOR skills/my-skill/SKILL.md
bash scripts/validate.sh

Skill directory names are kebab-case and must match the name field in SKILL.md. The validator enforces this in scripts/validate.sh.

Sync Vendored Skills¶

browser and browser-trace are tracked from browserbase/skills in skills.toml. Use vd to inspect and update tracked sources:

vd list
vd sync
vd doctor

vd doctor reports tracked drift plus hand-authored or detached skills. In this repo, most skills/* directories are intentionally untracked local catalog entries.

Release Changes¶

Use Conventional Commits. Release Please watches main and opens a release PR that keeps the skill-catalog version files aligned:

version.txt
skills.toml
.claude-plugin/plugin.json
.claude-plugin/marketplace.json
CHANGELOG.md

Source: .github/workflows/release.yml, .release-please-config.json, scripts/check-release-versions.sh.