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

flox-sharing

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

Quality

63%

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

Fix and improve this skill with Tessl

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

Quality

Content

57%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.

A well-structured, action-oriented Flox sharing/composition guide with strong concrete command and TOML examples. Its main weaknesses are repetitive examples that pad the token budget, absent validation checkpoints in the push/composition workflows, and a monolithic single-file layout with no progressive disclosure to bundle references.

Suggestions

Collapse the near-identical [include] TOML blocks (Full Stack, Reproducible stacks, Shared base configuration) into one example plus a short table of use cases to reduce redundancy.

Add an explicit validation checkpoint to the push workflow (e.g., run `flox list -c` or confirm the remote environment resolves before declaring success) so the sharing sequence has a feedback loop.

Move the detailed team-collaboration TOML patterns and the troubleshooting recipes into reference files under references/ and link to them from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly practical Flox-specific commands and TOML, but it repeats near-identical [include] blocks across 'Full Stack', 'Reproducible stacks', and 'Shared base configuration', and includes explanatory prose a competent Claude could infer, so it could be tightened.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready bash commands (flox activate -r, flox push, flox pull) and TOML snippets covering the common composition/sharing cases, with only minor gaps such as the `myproject_init() { ... }` ellipsis fragment.	4 / 5
Workflow Clarity	Sequences exist (the git-init/add/commit/push flow and the numbered troubleshooting steps), but there are no explicit validation checkpoints before outward-facing actions like `flox push`, leaving validation implicit.	3 / 5
Progressive Disclosure	No bundle files are provided, so this is a single ~425-line document; section headers and cross-skill references are clear, but detailed example sets and troubleshooting that could live in separate reference files are inlined.	3 / 5
	Total	13 / 20 Passed

Description

70%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 solid, third-person description that clearly defines the Flox sharing/composition niche with explicit 'Use for' trigger guidance and good natural keywords. It is held back from the top tier by somewhat abstract actions and 'when' phrasing that lists capabilities rather than concrete user-mention triggers.

Dimension	Reasoning	Score
Specificity	Names the domain ('Flox environments') and a couple of concrete actions ('Sharing and composing'), but the actions remain high-level and not comprehensive, matching the anchor that names domain plus 1-2 concrete actions.	3 / 5
Completeness	It states both what ('Sharing and composing Flox environments') and when ('Use for environment composition, remote environments, FloxHub, and team collaboration patterns'), but the 'when' lists capabilities rather than user-mention trigger phrases, so it is not quite the explicit-trigger anchor of 5.	4 / 5
Trigger Term Quality	Good natural-term coverage ('environment composition', 'remote environments', 'FloxHub', 'team collaboration') that a Flox user would actually say, with only minor synonyms missing, fitting the 'good keyword coverage' anchor.	4 / 5
Distinctiveness Conflict Risk	The Flox/FloxHub niche is mostly distinct, but sibling skills (flox-environments, flox-publish, flox-services) cover overlapping territory, giving minor overlap risk with closely related skills rather than minimal conflict.	4 / 5
	Total	15 / 20 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: aaa5f1a

Reviewed: 15 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.