Name: flox-sharing
Rating: 65.60000000000001 (1 reviews)
Author: flox

flox-sharing

Sharing and composing Flox environments. Use for environment composition, remote environments, FloxHub, and team collaboration patterns.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./flox-plugin/skills/flox-sharing/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with concrete commands and complete TOML examples, but it is over-long for a single SKILL.md with notable repetition and no bundle-file references to offload detail. Multi-step workflows also lack explicit validation checkpoints.

Suggestions

Consolidate the repeated [include] examples and the recurring 'See flox-environments skill for layering' pointers into one section to reduce token cost and lift conciseness.

Add explicit validation checkpoints to the push and composition workflows (e.g., 'flox activate -r owner/env to verify the pushed environment works' before declaring success) to support a validate→fix→retry loop.

Move the extensive example manifests and/or troubleshooting into a references file (e.g. references/composition-examples.md) with clearly signaled one-level-deep links so the SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~400-line body is mostly efficient, executable content rather than concepts Claude already knows, but it repeats the [include] environments pattern many times and re-states 'See flox-environments skill for layering' roughly six times, so it could be tightened.	2 / 3
Actionability	Provides fully executable flox CLI commands and complete, copy-paste-ready TOML manifest blocks with real field names (pkg-path, pkg-group, [include], [services.postgres], version), matching the anchor for fully executable, specific examples.	3 / 3
Workflow Clarity	Multi-step processes (push to FloxHub, base + specialization) are sequenced, but there are no explicit validation checkpoints or validate→fix→retry feedback loops; the guidelines cap workflow clarity at 2 when validation is missing for multi-step operations.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~400-line monolithic SKILL.md; section organization is good, but content that could be split (extensive example manifests, troubleshooting) is inline, matching the anchor for some structure with content that should be separate inline.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 concise, third-person description that clearly states both the skill's purpose and explicit use-conditions with distinctive Flox-specific triggers. Its only weakness is specificity, where it names the domain and a couple of actions rather than enumerating a fuller list of concrete capabilities.

Suggestions

Expand the action list to name more concrete capabilities (e.g., 'pull and activate remote environments, pin versions, compose base + specialization stacks') to lift specificity from 2 to 3.

Dimension	Reasoning	Score
Specificity	Names the Flox domain and two concrete actions ('Sharing and composing Flox environments') but does not enumerate multiple specific concrete actions, matching the anchor for naming domain and some actions without being comprehensive.	2 / 3
Completeness	Explicitly answers both what ('Sharing and composing Flox environments') and when via an explicit 'Use for ...' trigger clause, matching the anchor for clearly answering both what AND when.	3 / 3
Trigger Term Quality	Includes good coverage of natural terms a Flox user would say — 'environment composition', 'remote environments', 'FloxHub', 'team collaboration patterns' — with the distinctive proper-noun trigger 'FloxHub'.	3 / 3
Distinctiveness Conflict Risk	The Flox-specific niche and distinctive triggers ('FloxHub', 'Flox environments') make it unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flox/flox-agentic
Path: flox-plugin/skills/flox-sharing/SKILL.md
Commit: 84ba858

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.