beem-slide sync:skills

npx beem-slide sync:skills

Copies agent skills from a skills/ directory sitting beside the installed framework into .agents/skills/ in your workspace, and links .claude/skills/ at the same entries so Claude Code reads them too.

Read this before reaching for it

The published packages do not carry that directory. The authoring knowledge base is delivered live through the MCP authoring_guide tool to a signed-in account — it deliberately ships in no npm package and in no scaffold. So in a workspace installed from npm there is nothing for this command to copy, and the guides your agent should be reading come from beem mcp install instead.

The command remains useful where a skills directory is present next to the framework: a checkout of the framework repo, or a workspace where you maintain your own house skills in that layout.

What it writes, when there is something to write

.agents/
└── skills/
    └── <name>/        # the canonical copy
.claude/
└── skills/
    └── <name>         # symlink to ../../.agents/skills/<name>

Two directories because two conventions exist. The .agents copy is the real one; .claude points at it so both see the same files. Each skill is hashed before copying, so unchanged ones are left alone and only the links get refreshed. Where symlinks are unavailable — some Windows configurations — it falls back to a recursive copy.

Flags

Worth running first if the workspace has skills you edited by hand: the plan tells you what is about to be overwritten while you can still copy it somewhere.

The check on dev

beem-slide dev runs the same comparison at startup and offers to sync when it finds drift. With no skills directory to compare against there is nothing to report and it stays quiet. Where stdin is not a TTY it warns in one line rather than prompting. Suppress it with --no-skills-check, or BEEM_SLIDE_SKIP_SKILLS_CHECK=1 in a container build. See beem-slide dev.