flox-environments

Create reproducible, cross-platform (macOS/Linux) development environments with Flox, a declarative Nix-based environment manager. Use when setting up project toolchains for any language, installing system-level dependencies (compilers, databases, native libs like openssl/BLAS), pinning exact package versions for a team, running local services (PostgreSQL, Redis, Kafka), onboarding developers with one command, or solving 'works on my machine' problems — including agent/vibe-coding setups that need project-scoped tools without sudo. Also use when the user mentions .flox/, manifest.toml, flox activate, or FloxHub.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and well-structured content with executable examples and practical anti-patterns, though it leans slightly long and would benefit from splitting detailed recipes into reference files for better progressive disclosure.

Suggestions

Move the per-language recipes (Python/Node/Rust/Go/C++) and the Full-Stack Example into separate reference files under ./references/, keeping only one representative recipe inline in SKILL.md.

Tighten the AI-Assisted and Vibe Coding section by removing rationale bullets ('Why this matters for agents') that restate points already covered in 'When to Activate'.

Add an explicit validation checkpoint after destructive hook operations (e.g., verify initdb succeeded and pgdata is initialized before proceeding to service start).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste-ready manifest snippets and a useful anti-patterns section, but the AI-Assisted/Vibe Coding section restates motivations that Claude could infer and the Full-Stack Example repeats material from earlier recipes.	4 / 5
Actionability	Fully executable TOML blocks and shell commands cover the common cases (install, version pinning, platform-specific, services, language recipes), with concrete debugging commands and idempotency patterns included.	5 / 5
Workflow Clarity	Sequences are clear (init, edit manifest, activate, share via git/FloxHub) with debugging checkpoints, but destructive/batch operations like database init in hooks lack explicit validation feedback loops after initdb.	4 / 5
Progressive Disclosure	No bundle files exist; the body is a single monolithic document with all language recipes, anti-patterns, and a full-stack example inlined rather than split into separate reference files, which would be clearer for a skill of this breadth.	3 / 5
	Total	16 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that clearly states capabilities and trigger conditions with natural user-facing terms. Minor broadness in 'any language' framing slightly raises overlap risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (setting up toolchains, installing system-level deps, pinning versions, running services, onboarding), with only minor coverage gaps around build/packaging workflows.	4 / 5
Completeness	Explicitly answers 'what' (create reproducible cross-platform dev environments) and 'when' via multiple 'Use when' and 'Also use when' trigger clauses with concrete scenarios.	5 / 5
Trigger Term Quality	Comprehensive natural terms including file extensions/paths (.flox/, manifest.toml, flox activate), product names (FloxHub), and synonyms for the problem space ('works on my machine', toolchain setup).	5 / 5
Distinctiveness Conflict Risk	Clear Flox-specific niche with manifest.toml/.flox triggers giving low conflict risk, but the broad 'project toolchains for any language' framing could marginally overlap with language-specific package managers.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/flox-environments/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.