Do you need to install it?
- In a project, no.
npm create vfrey@beta my-channelalready puts the skill in the folder, in.claude/skills/vfrey/and.agents/skills/vfrey/, next toAGENTS.md,CLAUDE.md, andGEMINI.md. Open the folder in your agent. See the Quickstart. - Anywhere else, yes. If you work outside a project, or in a folder you did not make with
create-vfrey, install the skill once with the command below.
Install
Run this from any folder. Add--agent to pick your agent. The default is Claude Code.
- Claude Code
- Codex
- Grok
- Cursor
- Gemini CLI
- All five
claude session.Where the files land
By default the skill goes in your home folder, so every folder you work in has it. Add--project to put it in the current folder instead.
If another skill named
vfrey is already there, the install stops and prints a Fix: line. Add --force to replace it.
Any other agent
If your agent loadsSKILL.md folders, find its skills folder in its docs and pass that folder. --dir writes into PATH/vfrey, so pass the skills folder, not the vfrey folder.
--dir does not combine with --agent or --project. If your agent has no skills, see Any other agent.
Check that it is installed
skill: line lists each copy it found, and says whether it is up to date. If none is found, its Fix: line gives the install command.
Update
Install again. The skill is stamped with the package version it came from.@vfrey/ after npx if you are not in a project. The old copy is moved aside to vfrey.bak-DATE and the install prints where. Then restart or reload your agent as in the tabs above. A project made with create-vfrey carries its own copy. Update it with npx vfrey skill install --project from the project folder.
Uninstall
--agent, --project, and --dir flags as install. For example, npx @vfrey/vfrey@beta skill uninstall --agent codex.
For what the agent does with the skill, how it writes scripts and scenes, and per-agent notes, see Your agent.