Skip to content
Founding Lifetime: every skill, foreverFirst 100 members · $99 onceUpgrade
Lookbook
Sign In

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.

For
Anyone whose skill isn’t doing what they expect
Works with
Claude CodeCodexCursorGitHub CopilotGemini CLIOpenCodeAny agent that reads SKILL.md folders
Time
5 min read · updated Oct 26, 2026

The short answer

  1. Find the heading below that matches what you see. Each lists the most common cause first, with its fix.
  2. Most problems are a skill in a folder the agent doesn’t read, a session that started before the install, or a missing tool.

Three quick checks

Terminal
ls ~/.agents/skills/<skill>/SKILL.md ~/.claude/skills/<skill>/SKILL.md
curl -fsSL https://lookbk.dev/cli.js | node - list --installed   # add --project for this folder
node --version

The agent doesn’t see the skill

  • The session started before the install

    Start a new session. Claude Code also takes /reload-skills, and Copilot CLI and Gemini CLI take /skills reload. Restart Codex or Cursor if it still doesn’t appear.

  • The skill is in a folder this agent doesn’t read

    Claude Code reads .claude/skills; Codex, Gemini CLI and Copilot CLI read .agents/skills. Install again with --claude or --shared, or move the folder. See where skills live.

  • You installed into a project but started the agent elsewhere

    Claude Code, Codex and OpenCode look from where you start up to the repository root. Install with --project from that root and start the agent there.

  • The folder or file is wrong

    Unzipping a ZIP into a folder you made can give skills/<skill>/<skill>/SKILL.md. Move the inner folder up. The file must be named SKILL.md, with a name and description header starting on line one.

  • Agent-specific: trust and duplicates

    Gemini CLI loads workspace skills only in a trusted folder, so run /trust and restart. OpenCode reads both ~/.agents/skills and ~/.claude/skills and asks for unique skill names, so delete one copy.

It never runs on its own

  • Your request doesn’t match the description

    Agents compare your request with the description in SKILL.md. Lookbook descriptions end with the requests they are for, after “Use when” or “Use for”. Use those words, or call the skill by name.

  • Too many skills are installed

    Agents keep every skill’s description within a size budget: 1% of the context window in Claude Code, 2% in Codex. With many skills, descriptions get shortened or dropped. Remove skills you don’t use.

  • The agent is waiting for you

    Gemini CLI asks before it activates any skill, and OpenCode asks when its skill permission is ask. Approve the prompt.

  • Automatic use is switched off

    disable-model-invocation: true in a header, or allow_implicit_invocation: false in Codex, makes a skill run only when you call it.

To call a skill by name, see the cheat sheet.

A different skill runs

  • Another skill covers similar ground

    Two similar skills can match one request, and agents ship built-in skills of their own. Call yours by name, or switch the other off.

  • An older copy wins

    With the same skill in a personal and a project folder, Claude Code uses the personal copy, while Copilot CLI and Gemini CLI use the project copy. Compare versions, then update both or delete one.

Terminal
grep '"version"' ~/.agents/skills/<skill>/.lookbook/license.json .agents/skills/<skill>/.lookbook/license.json

The output looks generic or broken

  • The agent isn’t following the skill

    Signs: no brief file, no check step, default fonts. After Claude Code compacts a long conversation it keeps only the first 5,000 tokens of each invoked skill. Call the skill again, or start a new session.

  • Fonts or scripts didn’t load

    Many skills fetch Google Fonts and libraries such as GSAP from cdn.jsdelivr.net. If those are blocked you get system fonts or a still picture. Allow the hosts, or use the skill’s offline steps.

  • The agent edited the output, not the brief

    Lookbook skills keep your content in a brief, usually JSON, and a script writes it into the template. Hand edits can be overwritten, and in some video skills changing CSS colours does nothing. Change the brief and rebuild.

A render or export fails

Also search the skill’s own SKILL.md Troubleshooting section for the message.

Common render and export messages
MessageFix
ffmpeg not foundInstall FFmpeg, or set FFMPEG_PATH to it.
No Chrome found, or HyperFrames says Chrome is missingInstall Chrome, Chromium or Edge, or set CHROME_PATH. For HyperFrames, run the browser ensure command in the skill’s “What you need”.
The render hangs, or sub_timeline_script_failureGSAP didn’t load from cdn.jsdelivr.net. Allow the host, or copy GSAP into the project as the skill describes.
PptxGenJS is not installedRun npm i pptxgenjs@4.0.1 in the folder you run the export from.
record: the effect didn’t startChrome has no WebGL, or couldn’t load three.js from jsDelivr. Without a GPU the recorders use a slower software renderer; if that fails, set CHROME_PATH to another Chrome.

Works locally but not in a cloud agent

  • Personal skill folders stay on your computer

    A cloud agent starts from a copy of your repository. Install the skill into the repository and commit it. Skills are licensed to your account, so read the terms before you commit one to a repository other people can read.

  • The network is locked down

    The installer needs lookbk.dev, and many skills fetch from fonts.googleapis.com and cdn.jsdelivr.net. Allow those hosts, or commit the skill. Claude Code takes extra hosts under its Custom network level, Codex under Additional allowed domains. Copilot cloud agent warns in the pull request when its firewall blocks a request.

  • Tools are missing

    Claude Code’s list of cloud tools doesn’t name FFmpeg or Chrome. Install what the skill needs in the environment’s setup script.

  • There is no terminal for sign-in

    The installer prints the link and exits with code 3. Approve it on any device, then run the same command again.

From the repository root
curl -fsSL https://lookbk.dev/cli.js | node - add <skill> --project
git add .agents/skills/<skill> .claude/skills/<skill>
git commit -m "Add <skill> skill"

The install command fails

Installer messages and what to do
What you seeWhat to do
node: command not found, or lookbk: fetch is not definedInstall Node.js 20 or newer. Versions before 18 have no built-in fetch.
A sign-in link, then the command stopsNot an error. Approve in the browser, check the code matches, and run the same command again.
lookbk: the code expired. or sign-in was deniedCodes last 10 minutes. Run the command again and choose Approve.
lookbk: <skill> is a Pro skill.Buy it or get Pro at the link shown. If you have, run whoami to check the account, then logout and login to switch.
lookbk: no skill called "<skill>".Check the spelling against the list command.
… is still being built, … files aren’t published yet, could not start sign-in or download failedTry again in a moment. If a skill is still being built, it can’t be installed yet.

Still stuck?

Email support@lookbk.dev with your agent and its version, your operating system, and the command you ran with its full output.

Common questions

How do I see what my agent has loaded?
Claude Code and Codex: /skills. Copilot CLI and Gemini CLI: /skills list. Cursor: Customize, then Skills. OpenCode: ask the agent.

Sources

What this guide says about other companies’ tools comes from their own documentation, checked on Oct 26, 2026.

Did this guide help?

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.