CLI reference

fleet skills

Name: Fleet
Author: Fleet

fleet skills <list|install> [--target <dir>] [--dry-run]

Manages the Fleet skill library: fleet skills list prints the vendored skill names compiled into the binary, and fleet skills install syncs them to ~/.claude/skills/fleet/ where Claude Code can discover and run them. Skills are reusable workflow scripts (/fleet-dev-task, /fleet-review-pr, /fleet-ship-pr, /fleet-create-ticket, /fleet-hire) that agents invoke for structured work.

Re-run fleet skills install after every fleet upgrade to pick up skill fixes that ship with the new binary. Use --dry-run to preview the file list without writing.

Flags

--target <dir>	With install, write to a directory other than ~/.claude/skills/fleet/
--dry-run	With install, print the file list that would be written without writing anything

Examples

List vendored skill names

fleet skills list
# fleet-create-ticket
# fleet-dev-task
# fleet-hire
# fleet-review-pr
# fleet-ship-pr

Install all skills to the default location

fleet skills install
# Installed 12 skill file(s) to ~/.claude/skills/fleet
#   - fleet-dev-task

Preview what install would write

fleet skills install --dry-run
# Plan: 12 file(s) would be written under ~/.claude/skills/fleet
#   + ~/.claude/skills/fleet/fleet-dev-task/SKILL.md (4210 bytes)
# (dry-run — no files written)

Frequently asked questions

Where is the canonical source for Fleet skills?

Skills are vendored in the binary from internal/skills/fleet/<name>/SKILL.md via go:embed. The installed copies are generated from those embedded files.

Does fleet skills list show versions?

No. `fleet skills list` prints bare skill names, one per line, in sorted order. There is no --json flag.

Related commands

fleet init →fleet agent →fleet mcp →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet