The agent skillOptional

Add the Shed agent skill.

Optional. It teaches your coding agent to write a SHED file and run the CLI.

An agent that has never seen Shed will guess: SHED file keys that do not exist, CLI flags that were never added. The skill is what it reads before it acts.

It is plain files on disk following the Agent Skills specification. No service, no API key. Claude Code, Cursor, and Codex read the same copy.

It does not install the CLI. The skill teaches an agent to drive shed; the binary still has to be there. Everything works without the skill, your agent just needs more hand-holding.

One installer, two places it can put the skill. Unlike curl and npm, this choice changes the result.

1. 01
   This machineOne clone in ~/.shed/skills, symlinked into every agent in your home directory. Every project you touch on this laptop sees it, and one command updates all of them. It does not travel to anyone else.
2. 02
   This projectA copy inside the repo, at .claude/skills/shed. It is committed, so teammates and CI agents get it by cloning. It only applies to that one project, and updating it is a per-repo job.

Running both is fine and common. When an agent works inside a repo that carries its own copy, that copy is the one it reads.

The default, so there is no flag to pass. git is the only requirement.

curl -fsSL https://raw.githubusercontent.com/shed-sh/cli/main/install-skills.sh | sh

1. 01
   It clones once, then linksThe skill is cloned into ~/.shed/skills and symlinked into ~/.claude/skills/shed, plus ~/.cursor and ~/.codex when those directories already exist. An agent you install next month will not be linked until you run the script again.
2. 02
   Check it workedls ~/.claude/skills/shed should list the skill files. Your agent picks it up on its next session, not the current one.
3. 03
   Rerun it to updateEvery agent points at the same clone, so a single git pull updates all of them at once. Rerunning the installer does that pull for you.

Same installer, run from the project root with --local.

curl -fsSL https://raw.githubusercontent.com/shed-sh/cli/main/install-skills.sh | sh -s -- --local

1. 01
   Run it from the project root--local goes after sh -s --, which is how the pipe passes an argument through to the script. To target a directory other than the current one, add --dir <path>.
2. 02
   Check what it wroteA copy at .claude/skills/shed, and at .cursor/skills/shed and .codex/skills/shed when those directories already exist. A real copy rather than a symlink, which is what lets it survive a clone.
3. 03
   Commit itCommit .claude/skills/shed so teammates get the skill when they clone. Rerun the installer to pull in a newer version, and commit that too.