Skip to main content
Skills are folders of instructions and resources that guide Fleet through a specific kind of work. Each Skill is a directory with a SKILL.md file whose YAML frontmatter has a name and a description.

Bundled Skills

Fleet ships three Skills with each release.

How Skills reach a Turn

  1. Before each Turn, Fleet syncs the bundled Skills, then your local Skills, into /workspace/skills on the Session’s Daytona Volume.
  2. Fleet advertises the catalog to the model. Code in root and child Sandboxes reads Skills with list_skills, use_skill, read_skill_reference, and run_skill_script. See Sandbox tools.
  3. When you set FLEET_TYPESAFE_API_KEY, Fleet also asks the TypeSafe model which Skills are relevant after routing. It preloads up to three relevant SKILL.md files into the Turn. Direct answers skip this step. If selection fails, the Turn falls back to the catalog.
Child agents always receive a copy of the Session’s skills/ folder.

Add your own Skills

Put each Skill in its own folder under .fleet/skills/ (storage.local_skills_dir).
.fleet/skills/quarterly-report/SKILL.md
Fleet validates every Skill before it syncs:
  • The folder name uses lowercase words separated by single hyphens, up to 64 characters, and matches name in the frontmatter.
  • SKILL.md starts with YAML frontmatter. description has 1 to 1,024 characters, and the instructions after the frontmatter aren’t empty.
  • Each file is at most 1,000,000 bytes. A sync holds at most 200 files and 5,000,000 bytes in total.
  • Symbolic links aren’t allowed.
A local Skill with the same name as a bundled Skill replaces it. When a bundled file changes in a new Fleet release, the new version replaces the Session’s copy. When one of your Skill files differs from the Session’s copy, the sync fails with Skill sync conflicts with existing session files instead of overwriting it.

Manage Skills from the terminal

The agent can write new Skills in the Sandbox with save_skill. Use /skills pull to keep them locally. A pull never overwrites a local file with different content. It fails with Skill export conflicts with existing local file instead.

Manage Skills over HTTP

Each route takes an optional session_id query parameter (default default) and returns 409 while a Turn holds that Session’s lock. See the HTTP API reference.
Last modified on October 20, 2026