creating-sbx-kits

Write a Docker Sandbox kit — a spec.yaml declaring setup steps, network permissions and credentials. Use when authoring or fixing a kit, choosing between kind mixin and kind sandbox, migrating a spec from schemaVersion 1 to 2, or a kit fails sbx kit validate.

Quality

90%

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

86%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 dense, expert-oriented guide that assumes competence, leads with executable commands and complete code blocks, and routes field-level detail to real one-level-deep references. Its main weakness is mild stylistic flourish and an implicit rather than enumerated validation feedback loop.

Suggestions

Tighten narrative asides (e.g. "Two independent authors discovered that asymmetry the hard way") into bare statements of the rule to recover tokens.

Render the validation loop as an explicit validate → read error → fix → re-validate sequence so the feedback path is unambiguous.

Consider a short ordered checklist at the top of "It loads or it doesn't" so the skeleton→validate→iterate→ship sequence is scannable as steps.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence throughout (no explanation of Docker, sandboxes, or YAML) and is information-dense, but carries occasional stylistic color ("Two independent authors discovered that asymmetry the hard way") that could be trimmed.	4 / 5
Actionability	It supplies copy-paste-ready, executable guidance throughout — `sbx kit validate`, `sbx run --kit`, `sbx policy log`, full permissions YAML blocks, and a complete launcher bash script — covering the common cases concretely.	5 / 5
Workflow Clarity	A clear topical sequence (skeleton → validate → four decisions → ship) with an explicit validation checkpoint ("Spend it after every edit: `sbx kit validate`") and a real-sandbox iteration loop, though the validate→fix→re-validate feedback loop is implied rather than spelled out as a numbered checklist.	4 / 5
Progressive Disclosure	The SKILL.md is an overview that signals one-level-deep references via markdown links to real bundle files — [assets/mixin-spec.yaml], [assets/sandbox-spec.yaml], [assets/sandbox-aware/spec.yaml], and [references/spec-fields.md] — each confirmed present, with detail appropriately split out.	5 / 5
	Total	18 / 20 Passed

Description

95%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, third-person description that pairs a concrete what with a multi-clause when covering authoring, fixing, migration, and validation failures. It is specific, distinctive, and trigger-rich, with only minor specificity gaps relative to the body's full scope.

Dimension	Reasoning	Score
Specificity	Names the domain ("Docker Sandbox kit — a spec.yaml") and several concrete actions ("declaring setup steps, network permissions and credentials"), but stops short of the fuller action list the body reveals, leaving minor coverage gaps.	4 / 5
Completeness	It explicitly answers both what ("Write a Docker Sandbox kit — a spec.yaml declaring setup steps, network permissions and credentials") and when ("Use when authoring or fixing a kit, choosing between kind mixin and kind sandbox, migrating a spec from schemaVersion 1 to 2, or a kit fails sbx kit validate") with concrete trigger phrases.	5 / 5
Trigger Term Quality	The "Use when" clause spans natural triggers a kit author would actually voice — "authoring or fixing a kit", "kind mixin and kind sandbox", "schemaVersion 1 to 2", and the failure trigger "a kit fails sbx kit validate" — covering synonyms, format names, and a command.	5 / 5
Distinctiveness Conflict Risk	The niche is sharply drawn by "Docker Sandbox kit", "spec.yaml", "kind mixin/sandbox", "schemaVersion", and "sbx kit validate" — terms unlikely to fire for any other skill, with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: slurpyb/sbx-agent
Path: skills/creating-sbx-kits/SKILL.md
Commit: cd8f798

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