flox-sharing

Coordinates multi-archive Docker builds with configurable execution modes.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/randoneering/nix-flake-mirror --skill flox-sharing-randoneering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flox-sharing
Source: https://github.com/randoneering/nix-flake-mirror/tree/main/home/programs/opencode/skills/flox/flox-sharing
Command: npx skills add https://github.com/randoneering/nix-flake-mirror --skill flox-sharing-randoneering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts the need to manually coordinate environment definitions into a streamlined workflow for sharing and composing Flox environments, enabling teams to reuse base configurations and compose project-specific setups.

Core Features & Use Cases

  • Share base and specialized environments via .flox/ directories
  • Compose environments with include/ remote references and versioning
  • Collaborate using Git and FloxHub for runtime versus development patterns

Quick Start

Create and share a Flox environment by committing the .flox/ directory to your project and pushing with flox push.

Frequently Asked Questions about flox-sharing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share Flox environments with my team?▼

Share Flox environments by committing the .flox/ directory to your project and using flox push to collaborate via FloxHub or Git for runtime versus development patterns.

What is the best way to compose multiple Flox environments for a multi-project setup?▼

Compose Flox environments by structuring .flox/ directories with include and remote references, allowing teams to reuse base configurations and apply project-specific setups with versioned environment references.

Does Flox environment composition support idempotent hooks and manifest versioning?▼

Yes, Flox environment composition supports manifest composition, namespace practices, idempotent hooks, and versioned environment references to ensure consistent team-driven workflows.

Can I reuse remote Flox environments across different projects?▼

Yes, remote environment reuse is supported by structuring .flox/ directories and composing environments with include and remote references via FloxHub or Git repositories.

How do I structure .flox/ directories for team-driven Flox environment patterns?▼

Structure .flox/ directories by applying namespace practices, manifest composition, and idempotent hooks, with optional scripts, references, and assets directories for organized team collaboration.