SKILLEMALL.ai

BB flox-environments

Create reproducible, cross-platform (macOS/Linux) development environments with Flox, a declarative Nix-based environment manager. Use when setting up project toolchains, installing system-level dependencies (compilers, databases, native libs), pinning exact package versions for a team, onboarding developers, running local services (PostgreSQL, Redis, Kafka), 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.

affaan-m/everything-claude-code Agent Skills author: affaan-m MIT 1 file body ≈ 3 361 tokens Open the sourcegithub.com↗ analyzed 25 h ago

Create reproducible, cross-platform (macOS/Linux) development environments with Flox, a declarative Nix-based environment manager.

As a process B 66/100 · Nearly there — weak spots: result and completion, progress reporting

GeneratorPostgreSQLKubernetesSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Tools and files w 18
60
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ECC

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 66/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 60Failures and branches. 2 branches
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 23 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3361 tokens
    • 100Running it twice. Mutating operations check current state
    • low 13 top-level sections: this looks like several domains in one skill
    • high The skill tells the model to perform an irreversible action with no human approval

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • +1No license
    • +2Single-language instructions
    • +3Description length 567: enough signal without eating the budget
    • +4Structure: 30 headings
    • +3Step-by-step instructions: 23 items
    • +4Has examples (25 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.