Concepts
Agent Skills
Write your agent skills once, in a package in your configuration folder.
Every workspace that uses the package gets the same skills on the next
devmachine sync — Claude Code, Codex, Pi, OpenCode, Antigravity, Kimi
Code, and Cline all read them.
Your own computer gets them with devmachine skills add --package <name>. Edit one skill, sync again, and the change reaches every
workspace and your computer alike, from one place.
A skill is a folder of know-how your coding agent can read. Add the official set — devmachine’s own skills for operating the CLI — with:
devmachine skills add
See shared skills for every workspace for a full walkthrough with a package of your own.
One shared copy
Devmachine installs skills once, under ~/.agents/skills/<skill>/.
Codex, Pi, OpenCode, and Kimi Code read that folder directly. Claude,
Antigravity, and Cline don’t, so each gets a link that points to it, and
nothing is duplicated:
~/.claude/skills/<skill> -> ../../.agents/skills/<skill>
~/.gemini/antigravity-cli/skills/<skill> -> ../../../.agents/skills/<skill>
~/.cline/skills/<skill> -> ../../.agents/skills/<skill>
Devmachine never replaces a file or folder it didn’t create there: if
one is already in the way, skills add stops and names it.
Skills on your computer
devmachine skills add # the official set
devmachine skills add --package team-skills # skills from your own package
devmachine skills list
devmachine skills update
devmachine skills remove <skill>
--package installs skills from one of your own packages instead of the
official set. None of these commands touch a machine.
Skills in a workspace
A workspace gets skills only when you add the package to it, and run
sync:
devmachine packages add team-skills --workspace acme
devmachine sync --tags team-skills
A link is added only for a workspace that also has the agent’s package:
the Claude link with claude-code, the Antigravity link with
antigravity, and the Cline link with cline. Removing the package from your configuration doesn’t
delete files already on the machine.
Writing your own package of skills
A package can add:
skills:
path: skills
Every folder directly inside skills/ must be a complete skill, with
its own SKILL.md. See
the package format for the rest of
what a package can declare.