Floom Starter Pack

Quickstart

The simplest path is to paste one prompt into your agent (Claude Code, Cursor, Codex, OpenCode, Kimi). Your agent reads the manifest and installs the right files for its runtime. No account. Nothing to configure.

Set up Floom Starter Pack: https://floom.dev/docs#quickstart

Or run the CLI locally for all eligible agents on your machine:

npx @floomhq/starter install --global

The CLI detects which agent config paths exist on your machine and writes only to the appropriate locations. Folder-based skills also receive upstream support files when available. Omit --global when you want a project-local install in the current repository.

What gets installed

The pack writes three things per supported agent:

No executables. Nothing is added to your PATH, no daemons start, and no network connections stay open after install. The pack is static config and skill text.

Verified full-pack size on disk: about 924 KB for one agent plus a 32 KB local manifest.

Supported agents

The pack supports five agents out of the box. Each reads skill context from a different path. When you run the installer, it detects which directories exist and writes only to those. If none are found, it prompts you to choose.

Project-local installs use the same skill folders under the current repository. Codex is the exception for activation: it writes the Floom block into ./AGENTS.md, because Codex does not load ./.codex/AGENTS.md.

Not included: Gemini CLI is not supported in this pack at this time.

Updating

The package updates only when you ask it to. To pull the latest manifest and skill content:

npx @floomhq/starter update

This reads your existing .floom/manifest.json, checks the latest manifest, and rewrites only skills whose upstream content is newer. Existing user-modified skill files are preserved unless you pass --force.

Update Floom Starter Pack to latest: https://floom.dev/docs#updating

Or pin the install to a specific subset of skills/profiles when refreshing:

npx @floomhq/starter install --profiles core,dev --harness claude,codex

Idempotent. The collision check skips skills you have customised so re-running the command will not overwrite local edits. Add --dry-run to preview the plan without writing.

Uninstalling

Remove everything the pack added:

npx @floomhq/starter uninstall --global

Deletes the .floom/ directory and removes the Floom activation block from AGENTS.md / CLAUDE.md. Will not remove unrelated files.

Remove specific skills, an entire profile, or one agent only with remove:

npx @floomhq/starter remove --skills find-skills,brainstorming

npx @floomhq/starter remove --profiles dev

npx @floomhq/starter remove --all --harness claude

Use --global with any install, update, remove, or uninstall command to write/remove the pack at the user level (~/.claude/, ~/.codex/) instead of the current project.

Privacy

The Floom Starter Pack is a local install. After the initial download, it operates on your machine.

• No telemetry. No analytics. No usage data is collected or transmitted.
• No account, sign-in, or API key is required for the pack itself.
• The installer downloads skill files from GitHub. After install, there are no ongoing network calls by default.
• Skill files are static text. They contain no code that executes automatically.
• The find-skills meta-skill searches the local Floom-installed manifest and skill files. It does not call external registries unless you explicitly ask the agent to broaden discovery.

License

The Floom Starter Pack installer and tooling is MIT licensed. You can use, modify, and redistribute it freely per the repository LICENSE.

Individual skills in the pack carry their own licenses. Breakdown across the 65 curated skills:

Each skill file includes a license header. If you redistribute individual skills, preserve the header.

Architecture

The technical shape of the pack: how the installer resolves targets, what files get written, how agents discover installed skills, and what V0 guarantees.

Mental model

The package contains a manifest plus bundled skill folders. The installer resolves selected profiles, detects local agents, writes skills into their native roots, writes a local index, and adds instructions that teach agents to search locally.

V0 scope. Local compatibility infrastructure: curated skills without mandatory cloud accounts or MCP for the baseline discovery loop.

Install flow

When the user runs install, explicit targets win. If no target is passed, the CLI detects local agent config directories and installs only to those agents.

npx @floomhq/starter install --profiles core,dev,writing --harness claude,codex --yes

1. If --harness is provided, use the requested agents.
2. Otherwise, detect local agent config directories: ~/.claude, ~/.codex (or CODEX_HOME), ~/.cursor, ~/.config/opencode, ~/.kimi.
3. If any are found, install only to detected agents.
4. If none are found and the current directory looks like a project, install Claude Code by default after confirmation or with --yes.

By default, install writes all 65 curated skills. Use --skills <list> or --profiles <list> for a smaller subset. Use --global to write to user-level paths (~/.claude/ etc.) instead of the current project.

Files written

Each target receives skill files in its native root, a harness instruction file, and the shared local install manifest at .floom/manifest.json or ~/.floom/manifest.json when --global is used.

Conflict protection

Collision protection is content-based. If a target skill file already exists and differs from the bundled version, Floom keeps the user's file unless --force is passed.

1. Plan a skill write. If the destination does not exist, write the file.
2. If it exists and the content hash matches, skip it as already current.
3. If it exists and the content differs, keep the local file and print a warning.
4. If --force is passed, replace the target file explicitly.

Skill discovery

No MCP is required in V0. The discovery loop is local: injected instructions point the agent at the local activation list, .floom/manifest.json, and the find-skills meta-skill.

The agent reads the injected instructions, uses those trigger descriptions and the find-skills meta-skill, then loads the matching local SKILL.md or Cursor .mdc file on demand.

MCP can augment search for larger libraries later. It is not a launch dependency for Floom Packs V0.

Data model

The manifest links profiles to skills, and skills to upstream source records, keeping provenance legible and auditable.

Verified behaviors

Behaviors confirmed across all five launch targets. These are release acceptance criteria:

• Manifest references existing skill folders.
• Every bundled skill has frontmatter and description.
• Dry-run writes nothing.
• Temp-root install writes skills, manifest, and instructions.
• Target autodetection works.
• Missing detected targets produces a clear error.
• --harness claude,codex,cursor,opencode,kimi writes all five launch targets.
• Untracked existing skills are not overwritten.

Methodology

Why we built it this way: curation, activation, and what Floom adds versus upstream catalogs.

How we curated the 65-skill pack

Floom starts from the public skills ecosystem, including skills.sh, which indexes on the order of 91,000 skills, plus a small set of licensed benchmark and workflow sources. This pack ships 65 skills selected for broad usefulness, clean provenance, and zero-setup installation.

1. Usage signal: skills from skills.sh have strong install counts as a proxy for real-world validation. The pack favors skills with broad adoption over niche personal dotfiles.
2. License compliance: bundled skills must have a redistributable license or be Floom-maintained. Skills with unclear redistribution rights stay out of the public pack.
3. Description quality: skills need a clear "when it fires" trigger. Skills without an obvious trigger waste context and are not invoked reliably.
4. Zero setup: skills that require external credentials, paid services, or narrow cloud/vendor assumptions are excluded or replaced with simpler alternatives.

The source tiers, in priority order:

How activation works (the 100% pattern from Vercel)

Vercel published research that agents skip about 56% of installed skills by default. Even with an explicit "use these skills" prompt, invocation may only reach about 70%. The AGENTS.md activation pattern can reach 100% in their evals, see Vercel's agent evals post (same pattern Anthropic documents for Claude Code).

The pattern embeds per-skill trigger conditions in the agent context file (CLAUDE.md or AGENTS.md) instead of only saying "you have N skills installed."

1. Installer writes activation: each skill gets one or two trigger sentences, for example: when the user mentions test failures, invoke systematic-debugging.
2. Compact manifest: .floom/manifest.json holds installed skill names, versions, and target paths. Agents do not load every full skill file until invoked.
3. find-skills (Vercel Labs): when no installed trigger matches, the agent can search without loading every skill into context.
4. Load on demand: the full SKILL.md enters context when a trigger fires (Simon Willison: "skills cost a few dozen tokens until invoked").

Why curation beats quantity

The SkillsBench paper ( arxiv.org/abs/2602.12670 ) tested three installation strategies. Reported direction:

Irrelevant skills widen the option space the model must search. Kitchen-sink installs can force evaluation of hundreds of options per task, increasing latency and errors. Profile tags narrow what lands in activation so the agent sees relevant triggers first; find-skills can reach the rest when needed.

What Floom adds to upstream skills

Floom does not author most skills in the pack. Floom curates from the open ecosystem and adds five things on top:

1. Activation rules per skill in AGENTS.md / CLAUDE.md so they fire. Vercel reported this lifts activation from about 53% to 100% in their setup.
2. Cross-agent format translation: same skill, native install paths for five agents.
3. License vetting: exclude API-key and ambiguous-license skills.
4. Manual update and version tracking from upstream sources.
5. Curated portfolio: a small slice from a very large public index.

You get the original author's skill plus Floom's activation, packaging, and update layers. Each skill links to its source repository; Floom does not sit between you and the author's code.

Why Floom doesn't pay for inference

Skills run inside your agent, on your API key, using your token budget. Floom is distribution: manifests, installers, activation, and curation, not model inference. That is intentional: skills in your agent can use your filesystem, git repo, and project context; skills on a third-party runtime generally cannot.