flox-publish

Publishes user packages to Flox catalogs for distribution and reuse.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flox publishing streamlines distributing built artifacts from development to runtime by packaging, validating, and publishing to catalogs.

Core Features & Use Cases

  • Publish single or multiple packages to Flox catalogs for organization-wide reuse.
  • Validate builds and manage metadata so runtime environments can install reproducible artifacts.
  • Use cases include sharing internal tools, libraries, or CLI utilities via FloxHub.

Quick Start

Publish a prepared package to Flox to make it available for runtime installation.

Frequently Asked Questions about flox-publish

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

FAQPage Schema
How do I publish built packages to a Flox catalog?

To publish packages to a Flox catalog, you need a prepared build and the required publish metadata. This Skill automates the packaging and publishing process to make your artifacts available for runtime installation.

What do I need to share Flox packages across different teams?

Sharing Flox packages across teams requires a defined manifest, runtime-packages, and publish metadata. This Skill enforces this packaging discipline to ensure your built artifacts are reproducible and reusable.

Can I publish multiple packages to FloxHub at the same time?

Yes, you can publish single or multiple packages to Flox catalogs simultaneously. The workflow validates builds and manages metadata so runtime environments can install reproducible artifacts organization-wide.

Does Flox publishing validate builds before distributing artifacts?

Flox publishing validates builds and manages metadata to ensure runtime environments can install reproducible artifacts. This streamlines distributing built artifacts from development to runtime by packaging and validating before publication.

Why does my Flox workflow require specific metadata to publish?

Flox workflows require specific metadata to enforce packaging discipline and ensure reproducibility. A defined manifest, runtime-packages, and publish metadata are mandatory to successfully distribute built artifacts via catalogs.

What is the best way to distribute internal CLI utilities using Flox?

The best way to distribute internal CLI utilities is by publishing them to Flox catalogs via FloxHub. This allows organization-wide reuse and runtime installation of your validated, packaged artifacts.