Flox Environments
Reproducible cross-platform dev environments with Flox, a declarative Nix-based manager.
- What
- Reproducible cross-platform dev environments with Flox, a declarative Nix-based manager.
- Cost
- Free
- Needs
- Use "Flox Environments" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a guide to creating reproducible development environments with Flox, a declarative environment manager built on Nix with access to over 150,000 packages. One TOML manifest defines the whole toolchain, and every developer on the team gets identical packages, tools, and configuration across macOS and Linux, without containers or VMs. The skill covers the cases where Flox earns its keep: system-level packages (compilers, databases, native libraries) alongside language dependencies, exact version pinning for a whole team, onboarding new developers onto a working setup in minutes, running local services like PostgreSQL, Redis, or Kafka, and killing "works on my machine" for good, including agent and vibe-coding setups that need project-scoped tools without sudo. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the Flox CLI must be installed (free and open source); macOS and Linux only, no Windows support. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseWe automatically scan every listing and flag anything suspicious, but we can't review every line of community code. Here's how to check a build yourself before you install it.
Use "Flox Environments" with your Muse. Prerequisites: the Muse app (mobile or web), and the Flox CLI installed (free, open source) on macOS or Linux. Pure guidance skill beyond that. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/flox-environments/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Define a Flox manifest for [project]: I need [Python 3.11, PostgreSQL 16, Redis, Node 20, ...] pinned, plus local services for dev." 3. Ask Muse to write the manifest.toml, then walk through `flox activate` and verifying each tool resolves to the pinned version. Tip: start from the services, not the languages. Pinning PostgreSQL and Redis versions kills more "works on my machine" bugs than pinning the language runtime. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any generated manifest before activating it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.