Skip to main content
<- Docs home

Guides

Install Skills in Claude Code

Use Fygment setup, install, and check commands with Claude Code. Claude Desktop connects through the hosted connector instead.

Audience
Claude Code users who use Fygment-managed Skills.
Updated
2026-10-25

Claude Code follows the same workspace-approved package model as Codex, with local writes kept explicit and previewable.

Get the fygment command

Run npm install -g fygment once. After that, run fygment followed by a command, such as fygment setup.

npx fygment <command> also works if you prefer not to install the package. Running npx fygment by itself does not put fygment on your PATH.

Claude Code setup commands

fygment setup --target=claude-code

Sign in, choose a workspace, and select Claude Code as a local target. Setup also connects Fygment MCP and installs the companion Fygment Skill.

fygment install <skill-slug> --target=claude-code

Install one approved Skill into Claude Code. If you leave out --target, the install still goes to Claude Code. In a non-interactive shell, add --yes.

fygment check --target=claude-code

Check whether local Claude Code installs are current, stale, blocked, or require action.

Claude Desktop

Claude Desktop connects differently

Claude Desktop is an install target (--target=claude-desktop), but setup does not offer it. To connect Claude Desktop to Fygment, follow the Claude Desktop connection guide at /docs/mcp/connect/claude-desktop.

Common Claude setup issues

The Skill does not appear in the expected Claude Code target.

Check: Confirm the setup command selected the same target you are opening.

Next: Run check for that target and reinstall only after the package state is approved/current.

Related docs

  • CLI reference

    The CLI is the local bridge between a governed workspace and writable AI harness targets. Use it for setup, install state, update checks, setup checks, and selected imports.

  • Set up Fygment MCP

    MCP setup gives AI clients access to workspace-scoped Fygment tools. Hosted clients use OAuth; local clients use guided setup and a local authenticated proxy where needed.

  • Review and approve Skills

    Members can use the Skills they import right away. Review is for sharing more widely and for new versions. Each decision is made by someone with authority over that Skill or team, and every version approval re-runs the trust review.