CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-review-sandbox

One-time setup of the sandbox prerequisites used by the reproduce-issue skill and the reproduce-verifier agent — Docker, the isolation runtime (gVisor on Linux / Colima on macOS), healthy container networking, and the nx-review-sandbox toolchain image (built from the repo's mise.toml). Idempotent; re-run any time to verify or repair. Use when the user says "set up the review sandbox", "install the sandbox prereqs", "build the sandbox image", or a reproduce-issue preflight reports something MISSING.

Quality

94%

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

88%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 strong operational runbook: fully executable commands for both Linux and macOS, per-step verification with a smoke test and explicit green criteria, and genuinely non-obvious operational rationale (unconditional image rebuild, minimal build context, read-only pnpm store). The only weaknesses are minor trimmable prose in the toolchain-image section and missed opportunities to offload background detail to reference files.

Suggestions

Trim the historical anecdote in section 4 ('went unnoticed for two weeks, costing ~25 minutes of package downloads on every review') to a single sentence stating the rule — an image from an older revision passes an existence check, so Docker's layer cache is the correct freshness gate.

Move the pnpm-store copy-up mechanics (~2.3 GB / ~12 s figures) and the store-poisoning security note from sections 4 and 6 into a short reference file (e.g. references/sandbox-internals.md), keeping SKILL.md focused on the setup steps.

Add a one-line preflight summary at the top mapping each symptom (docker MISSING, runsc MISSING, networking BROKEN) to its section number, so repairs can jump straight to the relevant step on re-runs.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands with brief, non-obvious rationale (e.g., 'never `.` (the repo root), which would ship the whole monorepo'), but a few passages could be trimmed — notably the anecdote 'which is exactly how an image predating the pnpm-store warming went unnoticed for two weeks, costing ~25 minutes of package downloads' and the dense copy-up cost prose in section 4. This is 'efficient; minor instances of over-explanation' rather than the lean every-token-earns-its-place anchor 5.

4 / 5

Actionability

Every step is backed by copy-paste-ready commands covering both platforms: 'docker info >/dev/null 2>&1', the full gVisor apt/gpg install block, 'sudo modprobe veth', 'bash tools/review-sandbox/build-image.sh', and the smoke-test 'docker run --rm $RUNTIME nx-review-sandbox:latest bash -c ...' with the RUNTIME placeholder resolved by an in-line comment. The common cases (Linux and macOS, present vs MISSING) are all covered.

5 / 5

Workflow Clarity

A clearly sequenced 6-step process with explicit validation: 'Run `uname -s` first', OK/MISSING checks at each step, a recovery loop ('Then re-check the runtime line above'), error-path handling for the BTF mismatch ('the running kernel no longer matches its on-disk modules ... **reboot**'), and a final smoke test with an explicit success criterion ('Green when: the kernel is NOT your host kernel, and node/java/dotnet report versions').

5 / 5

Progressive Disclosure

Sections are well-organized and appropriately command-first, with the only external pointers being repo scripts ('tools/review-sandbox/build-image.sh', 'tools/review-sandbox/sandbox prune') that are clearly signaled. However, at ~109 lines with no bundle references, some inline content — the multi-paragraph rationale in section 4 and the disk-reclamation/security notes in section 6 — could live in a one-level-deep reference file, leaving SKILL.md a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete capabilities, platform specifics, an explicit idempotency guarantee, and quoted natural trigger phrases covering user requests and a preflight-failure signal, all in third-person voice. It is longer than the reference examples but every clause is load-bearing rather than padded.

DimensionReasoningScore

Specificity

The description enumerates concrete, comprehensive capabilities: 'Docker, the isolation runtime (gVisor on Linux / Colima on macOS), healthy container networking, and the nx-review-sandbox toolchain image (built from the repo's mise.toml)', plus the 'Idempotent; re-run any time to verify or repair' behavior. It matches the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require minor gaps in coverage, which are absent.

5 / 5

Completeness

It explicitly answers both 'what' (installs/verifies Docker, the isolation runtime, container networking, and the toolchain image, idempotently) and 'when' via a concrete 'Use when the user says...' clause listing three trigger phrases plus the preflight-failure case. This matches the top anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes multiple natural user phrasings in quotes — 'set up the review sandbox', 'install the sandbox prereqs', 'build the sandbox image' — plus a programmatic trigger ('a reproduce-issue preflight reports something MISSING'). This comprehensively covers the natural terms and synonyms a user would say for this niche; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The description is scoped to a clear niche — prerequisites for the 'reproduce-issue skill and the reproduce-verifier agent' with named components (gVisor, Colima, nx-review-sandbox, mise.toml) — so it is clearly distinguishable from generic Docker/setup skills and has minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

nrwl/nx

Path

.claude/skills/setup-review-sandbox/SKILL.md

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.