Agent skills that follow the open Agent Skills spec — usable by Claude Code, Codex, and any compliant agent. Installed straight from GitHub, no npm. Pick a path below.
Every skill in this repo is a self-contained folder under skills/ with a SKILL.md inside, plus any references/ or assets/ it needs. Your agent reads that folder and gains the workflow.
Because a skill is only files, there's nothing to compile and nothing to run from a registry. The two automated paths below just move these folders into the place your agent already looks — and you can always do it by hand.
skills-ref. That's the standard the copy-into-any-agent promise rests on — any compliant agent reads the same folder.Clone the repo and run install.sh to copy skills in.
Every path is pure GitHub + git. None of them download or execute an npm package.
| For | You need |
|---|---|
| Path A | Claude Code installed and signed in. That's it — it fetches the repo itself. |
| Path B / C | git, plus a Bash-capable shell. macOS and Linux ship one; on Windows use Git Bash or WSL. |
Run this inside Claude Code. It clones the repo from GitHub and reads its plugin catalog — no npm, no registry.
/plugin marketplace add brandtam/skills
The repo ships as a single plugin named brandtam-skills in a marketplace named brandtam. Installing it brings in every skill at once.
/plugin install brandtam-skills@brandtam
Open the plugin menu to see it listed and enabled. The skills are now available to Claude by name, or via each skill's slash command.
/plugin
/plugin marketplace add brandtam/skills to refresh the catalog; Claude Code pulls the latest from GitHub. To remove it, open the /plugin menu and uninstall brandtam-skills.A normal git clone. The skills sit right there in skills/ for you to inspect before anything is installed.
git clone https://github.com/brandtam/skills.git cd skills
install.sh copies skill folders into ~/.agents/skills/. It's plain Bash — it only reads the folders next to it and copies them. Nothing is fetched or executed from the network.
./install.sh
./install.sh write-commit prepare-release
DEST=~/.codex/skills ./install.sh # Codex CLI DEST=~/.claude/skills ./install.sh # Claude Code
Restart Codex or Claude, or reload skills, so it re-scans the skills directory. The new skills are now available.
git pull inside the cloned folder, then run ./install.sh again. It replaces each skill folder cleanly.If you'd rather not run a script at all, copy any single skill folder into your agent's skills directory. This is the most transparent option — you can read every file first.
# from inside the cloned repo, pick whichever skill you want cp -R skills/write-commit ~/.codex/skills/
Destination depends on your agent: ~/.codex/skills/ for Codex CLI, ~/.claude/skills/ for Claude Code, or a shared ~/.agents/skills/ store symlinked into either. To remove a skill, delete its folder.
| Path | How to confirm |
|---|---|
| A | /plugin in Claude Code lists brandtam-skills as enabled. |
| B / C | ls the folder you installed into, e.g. ~/.codex/skills, shows each skill with its SKILL.md. |
ls -1 ~/.codex/skills
| Skill | What it does |
|---|---|
| prepare-release | Cut a release from pending changesets — version preview, changelog, archived notes, tag / GitHub Release steps. |
| write-changeset | Write or update a changeset for a PR or branch, scaffolding the workflow if it's missing. |
| write-commit | Generate structured commit messages and optionally commit — honors templates, requires your approval before committing. |
| uat | Run a user-acceptance-testing session: collect observations, grill for decisions, then generate a PRD. |
| resurrect-project | Revive a dormant project — survey the code as historical signal, interview on today's intent, scaffold a rewrite plan. |