CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnosing-sbx-sandboxes

Work out why a Docker Sandbox cannot reach a host, install a package, keep a file, or start at all. Use when a download or clone fails inside sbx, a credential is rejected, a sandbox is killed or stops on its own, or something written inside it disappeared.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent, tightly written diagnostic reference: executable commands and a symptom→cause table make it highly actionable, and it stays lean without padding. Workflow clarity and progressive disclosure land at 4 because the skill is a symptom-indexed knowledge base in a single file rather than a strictly sequenced, externally-split workflow.

DimensionReasoningScore

Conciseness

Lean and dense throughout: assumes Claude's competence, avoids basic-concept padding, and isolates the only date-sensitive material in a dedicated "Last verified" section rather than scattering it inline.

5 / 5

Actionability

Copy-paste-ready commands appear throughout (sbx policy log, sbx diagnose, sbx policy check network …, git config --add safe.directory …, rm -rf ~/.local/state/sandboxes/ …) alongside a concrete symptom-to-cause table, covering the common cases.

5 / 5

Workflow Clarity

A clear "Start here" entry point, symptom-organized body, and an escalation ladder ordered by destructiveness with safeguards (--preserve-secrets; "Stop everything with sbx reset first") and validation checkpoints (policy check before burning a sandbox; git -C … rev-parse to confirm). Capped at 4 because the body is a symptom-indexed knowledge base rather than a single strictly gated multi-step workflow.

4 / 5

Progressive Disclosure

No bundle files exist to split into, but the body is well organized into clear ## sections that aid navigation; cross-links point to sibling skills (creating-sbx-kits, creating-sbx-templates, governing-sbx-fleets) rather than nested bundle references. Good monolithic structure with minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

87%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 description that crisply answers both what and when for a well-scoped diagnostic niche, with concrete failure-mode triggers. Specificity is held to 4 only because every symptom funnels into a single "work out why" action rather than multiple distinct verbs.

DimensionReasoningScore

Specificity

Names the sbx domain and four concrete failure modes (cannot reach a host, install a package, keep a file, or start at all), but they all resolve to a single diagnostic action ("Work out why"), so it stops short of the multiple-distinct-verb comprehensiveness of a 5.

4 / 5

Completeness

Explicitly states both what the skill does ("Work out why a Docker Sandbox cannot reach a host, install a package, keep a file, or start at all") and when to use it ("Use when a download or clone fails inside sbx, a credential is rejected…") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "download or clone fails inside sbx", "credential is rejected", "sandbox is killed or stops on its own", and "something written inside it disappeared" give good coverage, though a few common synonyms or file/CLI extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (diagnosing Docker/sbx sandbox failures) with distinctive triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
slurpyb/sbx-agent
Reviewed

Table of Contents

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.