Floom Docs

Save once. Sync everywhere.

Floom keeps reusable agent skills versioned, searchable, shareable, and synced into the harnesses you use.

What is a skill?

A skill is a folder package: SKILL.md plus optional examples, scripts, references, and assets. It is portable context your agent can discover and use.

How Floom organizes.

A library is a top-level container. Folders group skills by category. Skills are self-contained packages with their own files.

LIBRARYFOLDERSKILLFILESPersonalmarketingbrand-voiceSKILL.mdvoice-samples/tone-guide.mdcodepr-review
  • Library — top-level container for a project or team.
  • Folder — category inside a library.
  • Skill — SKILL.md plus optional references, examples, scripts, and assets.
  • Files — the package contents synced to native agent folders.

SKILL.md anatomy

Frontmatter names the skill, describes when to use it, and carries version/type metadata. The body gives the agent the reusable workflow.

Manifest fields

Floom records slugs, hashes, versions, package files, visibility, and sync status so local folders and remote history stay aligned.

The Floom MCP

Lightweight by design: a small Node runtime that exposes lexical search, curated tags, and get_skill without making every session preload every skill.

npx -y @floomhq/floom mcp install

How sync works

Save once, publish a version, then pull sync writes the local native skill folders for Claude, Codex, Cursor, Kimi, OpenCode, and compatible harnesses.

Zero-preload search keeps sessions lean: agents call search_skills and get_skill when a task needs a skill.

CLI reference

Use floom init, publish, add, setup, sync, watch, doctor, list, info, search, and library commands from the terminal.

Packs and sharing

Public and unlisted links install without an account. Signed-in users can save, publish, and subscribe to libraries.

Supported agents

Claude Code, Codex CLI, Cursor, Kimi, and OpenCode are the launch surface.