Floom

Share AI agent skills with a link.

A Floom skill is anything you share to make an agent better at a job: brand voice knowledge, company facts, onboarding docs, sales workflows, coding standards, and later executable skills.

npm install -g @floomhq/floom
floom login
floom publish pr-review-brief.md
# -> https://floom.dev/s/ffas93ud

floom add https://floom.dev/s/ffas93ud
# -> adds pr-review-brief.md locally

Publish knowledge, instructions, and workflows from your terminal. Anyone can add and use them in their agent.

Floom Version 0 - Sharing is intentionally narrow: terminal publish, link share, local add. Markdown is the source interface. No dashboard, no marketplace, no hosted execution.

Floom Version 1 - Synchronization starts with a preview: floom sync, floom watch, folder-aware local writes, and MCP startup/poll sync for your own published skills. Full Version 1 can later promote hot reload, update propagation, dependency management, install tracking, semantic versioning, and rollback.

Floom Version 2 is Teams and the first company-testable loop: creator UI, receiver UI, skill labels, email invites and delivery, install/update tracking, and clear MCP onboarding.

Structure

• cli/ — Node 22 TypeScript CLI, published as @floomhq/floom

• mcp-sync/ — MCP server preview, published as @floomhq/floom-mcp-sync

• web/ — Next.js 16 app (landing page + API routes), deploys to Vercel

• supabase/ — SQL migrations for the existing skills_minimal schema

Later-Version Prototype Code

The repo still contains later-version prototype code. Those routes are dormant until a version explicitly promotes them.

Version 0 Endpoints

• POST /api/skills (auth required) — body { title?, description?, body_md, visibility?, asset_type?, source?, installs_as?, version? }

• DELETE /api/v1/skills/:slug (auth required) — creator soft delete

• GET /s/:slug.md — public raw markdown

• GET /s/:slug.json — public full record

• GET /api/me — current user (auth required)

Schema

skills_minimal.posts in the existing Supabase project. Slugs are short nanoid (8 chars). RLS denies direct reads from anon; the public endpoints use the service role to fetch.

V0 keeps the external noun skill, while storing generic metadata underneath: asset_type (knowledge, instruction, workflow, skill), source (markdown), and installs_as (claude_skill, memory, rule, codex_instruction, etc.). V0 also stores an optional version label from frontmatter or CLI flags. Version history, rollback, and update propagation are later-version features.

Deploy

# Backend (web/)
cd web && vercel --prod

# CLI publish
cd cli && npm publish --access public

Version 0 Scope

In scope:

• floom publish <file>

• Optional version labels from frontmatter or floom publish --version

• Shareable skill links

• floom add <url-or-slug>

• floom info <url-or-slug>

• floom delete <url-or-slug>

• Raw Markdown skill endpoint

• Minimal auth

Out of scope:

• Team dashboards

• Marketplace discovery

• Folders and tags

• Approvals

• Hosted execution

• Browser extension

Version 1 Preview Scope

In scope:

• floom sync

• floom watch

• MCP startup and polling sync preview

• Missing-file-only writes for your own published skills

• Local conflict protection

• Folder-aware writes from server metadata

Out of scope:

• Creator and receiver dashboards

• Email sharing and delivery

• Team libraries

• Version history and rollback

• Automatic local Markdown deletion

• Hosted execution

Full Version 1 later:

• Hot reload through MCP where supported

• Update propagation

• Dependency management

• Install tracking

• Semantic versioning

• Rollback