Get Floom working in under 3 minutes.
Install the CLI, add a shared skill without an account, publish your own Markdown skill, and give Claude or Codex one setup instruction.
Install the CLI
Floom starts as a terminal-native distribution layer for knowledge, instructions, and workflows.
Add a shared link
Anyone with the link can add the skill into their local agent setup without creating an account:
The skill writes to the configured local agent folder.
Sign in
Browser OAuth stores your Floom token locally for publishing your own skills.
Publish a skill
Two commands. npx -y @floomhq/floom init scaffolds a Markdown template; you edit it; npx -y @floomhq/floom publish uploads it.
Open pr-review-brief.md in your editor, write the knowledge / instructions / workflow you want to share, save it, then publish:
Floom returns a shareable link like https://floom.dev/s/ffas93ud.
Tell your agent where Floom writes
One-time setup: paste the line below into your agent's system prompt or memory file (Claude Code: ~/.claude/CLAUDE.md, Codex: ~/.codex/AGENTS.md) so it picks up locally installed skills automatically.
That's it. Whenever you run floom add <link>, the skill drops into that folder and your agent finds it.
Troubleshooting
Install path looks wrong
Run npx -y @floomhq/floom doctor to inspect target directory and CLI compatibility.
Skill didn't appear
Check the path printed by npx -y @floomhq/floom add, then run npx -y @floomhq/floom doctor. Sign-in is only needed for publishing.
Login keeps failing
Sign out + back in: npx -y @floomhq/floom logout && npx -y @floomhq/floom login. If browser OAuth doesn't open, paste the URL it prints into your browser manually.
Still stuck
Email hello@floom.dev with the output of npx -y @floomhq/floom doctor attached.