Add skills to your agent.
To add a skill to Claude Code, put its folder, with the SKILL.md inside, in .claude/skills/ in your project, then restart Claude Code. Codex, Cursor and other agents read .agents/skills/ instead. The Wensity CLI does this for you in one command, records what it wrote, and keeps your edits safe on every update. To see what each skill does, browse the skills.
Install
Free skills need no account:
pnpm dlx wensity@latest skills add typography
npx wensity@latest skills add typography
yarn dlx wensity@latest skills add typography
bunx wensity@latest skills add typography
They are also in the public wensity/skills repository, so npx skills add wensity/skills works too.
Pro skills come with Wensity Pro. Log in once with a dashboard token, then add them by name, or add --all for every skill your plan includes:
npx wensity@latest loginnpx wensity@latest skills add motion colornpx wensity@latest skills add --all
Names work in full (wensity-motion), short (motion), or as the page slug (ux-writing). Restart your agent, or start a new session, to load new skills.
With the Wensity MCP server connected, you can also just ask your agent to install a skill. It installs the same files, with the same rules.
Where skills are stored
| Agent | This project | Every project (--global) |
|---|---|---|
| Claude Code | .claude/skills/ | ~/.claude/skills/ |
| Codex, Cursor, Copilot, Windsurf, Gemini CLI, OpenCode | .agents/skills/ | ~/.agents/skills/ |
To add any other skill by hand, copy its folder into one of these. The CLI installs for the agents your project already uses. When it finds none it asks once, or installs for both with --yes. Pick yourself with --agent claude or --agent agents, or pass both.
Each install is recorded in wensity-skills.json at the project root (with --global, in ~/.config/wensity/skills.json), with a checksum for every file it wrote.
Update and remove
npx wensity@latest skills listnpx wensity@latest skills updatenpx wensity@latest skills remove motion
update gets the latest version, shows what changed, and skips any file you changed since the CLI wrote it, then tells you which. Add --force to replace them. remove deletes only files the CLI wrote and you have not changed. Add --dry-run to any command to see the changes first.
Each Pro file carries a license line for your account. Keep them out of public repositories. If a yearly plan ends, installed skills keep working, but updates and new installs stop. See the license.
Commands
| Command | What it does |
|---|---|
skills add <name...> | Install skills. --all adds every skill your plan includes. |
skills list | Every skill, Free or Pro, with installed and latest versions. |
skills update [name...] | Update installed skills, keeping files you edited. |
skills remove <name...> | Delete the files the CLI wrote. |
Flags: --agent claude|agents, --global, --dry-run, --yes, --force. See the CLI reference for the rest.
Troubleshooting
"This skill comes with Wensity Pro"
The account behind your saved login has no Pro plan. Check it with npx wensity@latest whoami, or see plans. Free skills still install without logging in.
"Your Wensity Pro access is not active"
The plan has ended, or access was paused. Skills you already installed keep working. See billing to renew.
"Your saved Wensity login was not accepted"
The token was revoked or replaced. Create a new one in the dashboard and run npx wensity@latest login again.
The agent does not see a skill
Restart it, or start a new session. Then check the folder in the table above matches your agent, and that SKILL.md is directly inside <folder>/<skill name>/.
"These files are already there and were not written by Wensity"
A skill folder already holds files the CLI did not install, for example from a manual copy. Add --force to replace them.
"is a symlink"
The CLI never writes through a symlinked folder. Point the link at a real folder, or remove it, and run the command again.