Install a skill in any agent
Install a Lookbook skill in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI or OpenCode: where each looks, how to check it loaded and how to run it.
- For
- Anyone installing a skill in a specific agent
- Written for
- Claude CodeCodexCursorGitHub CopilotGemini CLIOpenCodeAny agent that reads SKILL.md folders
- Time
- 5 min read · updated Oct 26, 2026
The short answer
- Run
curl -fsSL https://lookbk.dev/cli.js | node - add <skill>, or paste the skill’s install prompt into your agent. - Approve the sign-in link it shows, then start a new agent session.
- Check the agent lists the skill, and ask for the job in plain words.
What you need
- Node.js 20 or newer, for the installer.
- A Lookbook account. Every install signs in, free skills included.
- Whatever the skill itself needs, such as Chrome or FFmpeg. Its
SKILL.mdlists these under “What you need”.
The install command
Step 1: Run the command
Replace
<skill>with the last part of the skill page’s address, such askinetic-title-drop. It downloads the installer and runs it once. Nothing is added to yourPATH.TerminalStep 2: Approve the sign-in
The first time, it prints a link and a short code. Open the link, check the page shows the same code, and choose Approve. In your own terminal the command waits and carries on. In an agent’s shell it prints the link and exits with code 3, so run the same command again after you approve.
Step 3: Start a new session
The installer prints one
Installed … →line for each folder it wrote. Start a new agent session so it picks up the skill.
You can also copy the install prompt from the skill page and paste it into your agent. The agent runs the same command and shows you the sign-in link. For cloud agents, run the command from your repository root with --project, then commit the folders it writes.
Install by hand
Download the ZIP from the skill page while signed in. It holds one folder named after the skill, so unzip it straight into a skills folder and SKILL.md ends up one level down. Keep every file, including NOTICE.md and the hidden .lookbook folder.
Your agent
- Looks in:
~/.claude/skillsfor every project, and.claude/skillsin the folder you start in and each parent up to the repository root. Its docs don’t list.agents/skills. - Check: type
/skills, or ask “What skills are available?”. Claude Code watches its skills folders. If~/.claude/skillsis new, run/reload-skills. - Run: ask in plain words, or start a message with
/<skill>.
- Looks in:
~/.agents/skillsfor every repository, and.agents/skillsfrom the folder where you launch Codex up to the repository root. - Check: run
/skillsin Codex CLI or the IDE extension. Codex detects changes on its own; restart it if a skill is missing. - Run: type
$and pick the skill, or name it in your prompt, such as$kinetic-title-drop make a title drop that says “Ship it today”.
To turn a skill off without deleting it, add this to ~/.codex/config.toml and restart Codex:
- Looks in:
~/.agents/skillsand~/.cursor/skills, and.agents/skillsand.cursor/skillsin a project, including subfolders. For compatibility it also reads.claude/skillsand.codex/skills, at home and in projects. - Check: Cursor finds skills when it starts, so restart it. Then open Customize in the sidebar and choose Skills.
- Run: type
/in Agent chat and search for the skill. That applies it to one message. The agent also picks skills on its own. - Cloud Agents don’t get
~/.agents/skills. Install with--projectand commit the folder, or turn on Sync Skills for Cloud Agents, which syncs only~/.cursor/skills.
- Looks in (CLI):
~/.copilot/skillsand~/.agents/skillsat home;.github/skills,.claude/skillsand.agents/skillsin a repository. A project copy beats a personal one with the same name. VS Code also reads~/.claude/skills. - Check (CLI):
/skills list, or/skills info <skill>to see where it loaded from. After adding one mid-session, run/skills reload. From a shell,copilot skill list. - Check (VS Code): type
/in chat, or choose Open Customizations in the Chat view, then Skills. - Run: in the CLI, write
Use the /<skill> skill to …. In VS Code, type/and pick it. - Cloud agent: GitHub says not to assume a personal skill is available to an agent in the cloud. Install with
--projectand commit.
- Looks in:
~/.gemini/skillsor~/.agents/skillsat home, and.gemini/skillsor.agents/skillsin a workspace. A workspace skill beats a home one, and.agents/skillsbeats.gemini/skillswithin each.SKILL.mdmust sit atskills/<skill>/SKILL.md; deeper files aren’t found. - Check: run
/skills list, or/skills reloadafter installing. From a shell,gemini skills list. Workspace skills load only in a trusted folder: run/trustand restart. - Run: ask in plain words. Gemini CLI then asks permission to activate the skill and shows its name, purpose and folder. Approve it.
- Looks in:
.opencode/skills,.claude/skillsand.agents/skillsin a project, from your working folder up to the git worktree root, and~/.config/opencode/skills,~/.claude/skillsand~/.agents/skillsat home. - Check: OpenCode lists skills in its
skilltool’s description, so ask the agent which it can load. Start a new session after installing. - Run: ask in plain words. If your
opencode.jsonsets the skill permission toask, approve the prompt. - Two copies: the installer writes two when you also have Claude Code, and OpenCode reads both. Its docs ask for unique skill names across locations, so delete one copy if the skill doesn’t show up.
Common questions
- Which folder do I use if I switch agents?
- The installer’s default covers all six. Cursor, OpenCode and VS Code read both
~/.agents/skillsand~/.claude/skills; if one lists a skill twice, delete one copy. - Why did the install stop after printing a link?
- In an agent’s shell, the command can’t wait for you. Approve the link in your browser, then run the same command again.
- Do cloud agents see my installed skills?
- No. They start from a copy of your repository, so install with
--projectand commit the folder. Read the terms before you commit a skill to a repository other people can read.
Sources
What this guide says about other companies’ tools comes from their own documentation, checked on Oct 26, 2026.
- Claude Code: extend Claude with skills (opens in a new tab)
- Claude Code: commands (opens in a new tab)
- Claude Code: environment variables (CLAUDECODE) (opens in a new tab)
- Codex: build skills (opens in a new tab)
- Cursor: Agent Skills (opens in a new tab)
- GitHub Copilot CLI: adding agent skills (opens in a new tab)
- GitHub Copilot CLI command reference: skill locations (opens in a new tab)
- GitHub Copilot: about agent skills (opens in a new tab)
- VS Code: Agent Skills (opens in a new tab)
- Gemini CLI: Agent Skills (opens in a new tab)
- Gemini CLI: get started with Agent Skills (opens in a new tab)
- OpenCode: Agent Skills (opens in a new tab)
Did this guide help?
Read next
All guidesWhere skills live: folders for every agent
The folders each agent reads skills from, which copy wins when two share a name, and what cloud agents can see.
Skill not working? Find your symptom
Fix a Lookbook skill by what you see: the agent can’t find it, it won’t trigger, the wrong skill runs, output looks off, a render fails or install stops.
Update, roll back and remove skills
Update an installed skill, go back to the version you had, and remove or switch off a skill in Claude Code, Codex, Cursor, Copilot, Gemini CLI or OpenCode.
See a skill’s result before you install it.
Every skill page shows what it makes, what it needs and which agents can run it.