skills.rest
flox
floxOFFICIAL
Explore all skills by this author →
Website𝕏@floxdevelopmentGitHub

flox-publish

Publish built Flox packages to personal or organization catalogs after authentication and validation.

12|3|Updated Nov 6, 2025
Search Tags:#authentication#catalog#publish#namespace#package#flox#build-validation
One-click install
npx skills add https://github.com/flox/flox-agentic --skill flox-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flox-publish
Source: https://github.com/flox/flox-agentic/tree/main/flox-plugin/skills/flox-publish
Command: npx skills add https://github.com/flox/flox-agentic --skill flox-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishes built Flox packages to Flox catalogs for distribution and reuse, simplifying sharing of artifacts across teams and environments.

Core Features & Use Cases

  • Publish to personal and organization catalogs: Distributes binaries/artifacts to the appropriate Flox namespace for easy consumption.
  • Authentication and validation: Requires flox auth login and build validation prior to publishing to ensure reproducibility and security.
  • Artifact-only publishing: Ensures published packages contain binaries/artifacts and metadata, not source code, enabling clean runtime environments.

Quick Start

Authenticate with flox auth login, then publish your package with flox publish to your chosen namespace.

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 Flox packages, authenticate with flox auth login, validate your build, then use flox publish to distribute binaries and metadata to your chosen personal or organization namespace.

What is required to share Flox packages with an organization namespace?▼

Sharing Flox packages requires authentication via flox auth login, successful build validation, and properly structured artifacts with runtime dependencies and metadata before publishing to the namespace.

Can I publish source code to a Flox catalog for distribution?▼

No, Flox publishing requires artifact-only packages containing binaries and metadata, not source code, ensuring clean runtime environments for distributed packages across teams.

How does build validation work before publishing Flox packages?▼

Build validation ensures reproducibility and security by verifying package contents, including binaries, runtime dependencies, and metadata, before allowing flox publish to execute successfully.

Do I need to authenticate every time I publish to a Flox namespace?▼

Authentication via flox auth login is required prior to publishing Flox packages to ensure secure distribution to personal or organization catalogs within your namespace.

What's the best way to distribute Flox packages across multiple environments?▼

Publishing built Flox packages to catalogs simplifies distribution and reuse across teams and environments by applying packaging rules for binaries, artifacts, and runtime dependencies within your namespace.

Related Skills

Explore More Software Engineering Skills→
randoneeringrandoneering

flox-publish

Publishes user packages to Flox catalogs for distribution and reuse.

Community
Advanced
randoneeringrandoneering

flox-containers

Containerize Flox environments into portable Docker and Podman images.

Community
Intermediate
randoneeringrandoneering

flox-builds

Automate Flox-based manifest and Nix expression builds.

Community
Advanced
bpnrockstarbpnrockstar

supply-chain-attack-recon

Identify software supply-chain vulnerabilities in public GitHub repositories, Docker images, and SBOMs.

Community
Advanced