Metaplay Docs

Appearance

metaplay skills install [flags]

[preview] Install Metaplay skill wrappers into your project (or user home)

metaplay skills install [flags] ​

PREVIEW: This command is in preview and subject to change!

Install thin wrapper SKILL.md files for the embedded skills.

Project scope writes under the current directory. We do NOT walk up to a metaplay-project.yaml or git root, since the user may run their harness from a subdirectory. Pass -p/--project to target a different directory explicitly.

Each wrapper carries the CLI version that wrote it in its frontmatter. Subsequent installs only overwrite a wrapper if the current CLI is the same version or newer — running an older CLI against a project initialised by a newer CLI does not revert wrappers. User-authored skill files (those without 'managed-by: metaplay-cli') are never touched.

Targets:

  • 'standard' (.agents/skills/) — the cross-agent shared dir. At project scope, read by Cursor, Codex, GitHub Copilot / VS Code, Windsurf, Gemini CLI, OpenCode, Cline, Amp, Warp, and others that follow the open Agent Skills convention. At user scope, ~/.agents/skills/ is read by Codex, Cursor, Copilot, Windsurf, Gemini, Cline, and Warp.
  • 'claude' (.claude/skills/) — read by Claude Code.

User scope additionally offers per-harness home directories mirroring the vercel-labs/skills convention: cursor, copilot, codex, windsurf, gemini, junie, continue, cline, warp, goose, amp, opencode, augment, roo. Pick these for tools that don't read ~/.agents/skills/ (e.g. Junie, Continue, Roo) or when you only want to install for one specific tool.

Project-scope note: for tools that read from neither .agents/skills/ nor .claude/skills/ (e.g. JetBrains Junie, Continue, Roo Code), either copy/symlink the installed dir into the tool's expected location, or run the user-scope install and tick the tool directly.

In interactive mode, you'll be prompted first for the install scope (project or user) and then for the target dir(s); the default selection is based on which directories already exist.

Examples ​

sh
# Interactive prompts for scope and target.
metaplay skills install
# Install for Claude Code in the current project.
metaplay skills install --scope project --target claude
# Install both standard and Claude Code dirs at project scope.
metaplay skills install --target standard --target claude
# User-scope install for two specific tools.
metaplay skills install --scope user --target cursor --target junie
# Force-overwrite even wrappers stamped with a newer version.
metaplay skills install --force

Flags ​

  • --force: Overwrite even when the on-disk wrapper has a newer version stamp
  • --scope <string>: 'project' (current directory; or --project path) or 'user' (your home directory). Defaults to interactive prompt or 'project'.
  • --target <stringSlice>: Target dir(s). Repeatable. Project scope: standard, claude. User scope: standard, claude, cursor, copilot, codex, windsurf, gemini, junie, continue, cline, warp, goose, amp, opencode, augment, roo. Defaults to interactive prompt or detection. (default: [])

Inherited Flags ​

  • --color <string>: Should the output be colored (yes/no/auto)? [env: METAPLAYCLI_COLOR] (default: auto)
  • --project <string>: Path to the to project directory (where metaplay-project.yaml is located)
  • --skip-version-check: Skip the check for a new CLI version being available
  • --verbose: Enable verbose logging, useful for troubleshooting [env: METAPLAYCLI_VERBOSE]