Skills Commands Reference

Complete reference for all cmd skills commands. Install, list, and remove agent skills.

Quick Reference

Command	Description
`cmd skills add`	Install a skill from a GitHub repository
`cmd skills list`	List all installed skills
`cmd skills remove`	Remove an installed skill

Install a skill

Install a skill from a GitHub repository into your project or global skills directory.

Usage

cmd skills add

cmd skills add <owner/repo> [options]

Options

Option	Short	Description
`--global`	`-g`	Install to global skills (`~/.commandcode/skills/`)
`--force`	`-f`	Overwrite if skill already exists
`--skill <name>`	`-s`	Pick a specific skill from a multi-skill repo

Examples

Single-skill repo

cmd skills add acme/my-skills

Specific path in repo

cmd skills add acme/skills/path/to/skill

Pick one skill from a multi-skill repo

cmd skills add acme/multi-skills -s my-skill

Specific branch

cmd skills add acme/repo@branch

Install globally

cmd skills add acme/repo --global

Install locations

Flag	Location	Availability
(default)	`.commandcode/skills/<skill-name>/`	Current project only
`--global`	`~/.commandcode/skills/<skill-name>/`	All projects on your machine

Multi-skill repos

When a repo contains multiple skills and --skill is not specified, Command Code shows an interactive prompt to select which skills to install.

Name collisions

Skill names share the / menu with built-in commands (/clear, /help, /share, /rewind, …) and with the custom commands in .commandcode/commands/. Built-ins and custom commands take precedence — typing /<name> resolves to the owner, not to the skill.

If you install a skill whose name collides with one of those, cmd skills add still completes normally — nothing blocks the install. The skill then appears in the / menu with a [skill] badge and a shadowed by /<owner> note so you can see it exists, while /<name> continues to route to the higher-precedence owner.

See Selection priority for the full order.

List installed skills

List all installed skills, grouped by location.

Usage

cmd skills list

cmd skills list

Output

Shows all installed skills split into Project and Global sections:

Example output

Skills (3 installed)

Project (1)
  remotion-best-practices · Best practices for building Remotion video...

Global (2)
  frontend-design · Guidelines for building accessible, responsive UIs
  code-review · Comprehensive code review checklist for security and q...

If no skills are installed, the command shows where it looked and how to install one:

Empty output

No skills installed.

Looking in:
  ~/.commandcode/skills/ (global)
  .commandcode/skills/ (project)
  ~/.agents/skills/ (global, .agents)
  .agents/skills/ (project, .agents)

Install a skill: cmd skills add <owner/repo>

Uninstall a skill

Remove an installed skill by name. Prompts for confirmation before deleting.

Usage

cmd skills remove

cmd skills remove <skill-name> [options]

Options

Option	Short	Description
`--global`	`-g`	Remove from global skills (`~/.commandcode/skills/`)
`--yes`	`-y`	Skip the confirmation prompt

Examples

Remove from project

cmd skills remove remotion-best-practices

Remove from global

cmd skills remove frontend-design --global

Skip confirmation

cmd skills remove my-skill --yes

Skill name rules

Skill names must use lowercase letters, numbers, and hyphens only — no path separators, dots, or uppercase.

Next steps

Manage your skills — create and organize skills manually
Skills overview — learn how skills work
Best practices — write effective skills