finding-sbx-docs

Locate the official Docker Sandboxes page behind a claim, build or refresh the local mirror of the docs, and carry what changed upstream into the other sbx skills. Use when checking whether an sbx claim still holds, when `references/docs/` is missing, when an sbx release lands, or when a skill's verification date needs moving.

Quality

83%

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

75%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, executable skill body with concrete commands, clear multi-step workflows, validation checkpoints, and real bundle references. Slight conciseness and disclosure gains remain from trimming motivational prose and deferring script-internals detail.

Suggestions

Trim the motivational intro and the copyright/licensing aside to pure instruction, moving the licensing rationale to a short comment in fetch-docs.sh.

Move the relink-internals and shared-filename edge-case detail ('Several pages share a filename...') into a brief note in relink-docs.py or a references file, keeping the body as an overview.

Add an explicit validation command (e.g. re-running the diff or a check script) to the carry-changes workflow's final step to make its already-strong completion criterion a concrete verifiable checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no explaining of git/curl/diff), but the intro paragraph and a few motivational sentences ('Docker changes sbx often...,' the copyright/licensing aside) could be trimmed.	4 / 5
Actionability	Real executable commands throughout (curl with `.md`, the fetch script, `git diff`, `sbx --version`, `sbx <cmd> --help`) and an ownership table mapping pages to skills, with minor gaps where carry-change steps are guidance rather than a single script.	4 / 5
Workflow Clarity	Well-sequenced workflows with stop-conditions and an explicit completion criterion ('Done means every changed page is accounted for'), plus error-recovery notes (lock diff review, 'suspect the mirror before believing the diff'); the batch workflow's validation is present so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	Clear section headers and one-level-deep references to real bundle files (`references/docs.lock`, `scripts/fetch-docs.sh`, `scripts/relink-docs.py`, all verified present), with some inline script-behavior and filename-collision detail that could be deferred to a reference.	4 / 5
	Total	16 / 20 Passed

Description

92%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, specific description that clearly states what the skill does and gives multiple concrete 'when' triggers. Slightly specialized vocabulary keeps trigger-term coverage just short of fully comprehensive.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — 'Locate the official Docker Sandboxes page behind a claim,' 'build or refresh the local mirror of the docs,' and 'carry what changed upstream into the other sbx skills' — giving comprehensive coverage of the skill's purpose.	5 / 5
Completeness	Explicitly answers both 'what' (locate page, build/refresh mirror, propagate changes) and 'when' with a concrete multi-clause 'Use when...' trigger phrase.	5 / 5
Trigger Term Quality	Covers several natural trigger scenarios ('checking whether an sbx claim still holds,' 'when an sbx release lands,' 'when a skill's verification date needs moving,' '`references/docs/` is missing'), but the vocabulary is somewhat specialized and lacks plain synonym breadth.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche within the sbx docs ecosystem — doc location, mirroring, and cross-skill propagation — with triggers distinct from sibling sbx skills (running, creating, diagnosing).	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 6 missing, 5 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: slurpyb/sbx-agent
Path: skills/finding-sbx-docs/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.