SKILLEMALL.ai

CF sandbox-unblock

Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eight checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of method errors.

FlorianBruniaux/claude-code-ultimate-guide Agent Skills author: FlorianBruniaux CC-BY-SA-4.0 1 file body ≈ 2 108 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change.

As a process F 32/100 · No process to follow — References files that are not bundled: ../../../guide/security/sandbox-native.md, ../sandbox-status/SKILL.md, ../../config/sandbox-native.json

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
94
Quality 40%
59
Run on models
none yet
Process rating
F
32/100
No process to follow
References files that are not bundled: ../../../guide/security/sandbox-native.md, ../sandbox-status/SKILL.md, ../../config/sandbox-native.json
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Grep Bash
  • low Dangerous commands cmd-privilege SKILL.md:190
    Privilege escalation / world-writable permissions (documentation of a security skill)
    | Setuid binaries | `ps`, `top`, `su`, `login` cannot exec | `lsof -nP -iTCP -sTCP:LISTEN` |
    security skill

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../../guide/security/sandbox-native.md
  • warning missing-ref reference to a missing file: ../sandbox-status/SKILL.md
  • warning missing-ref reference to a missing file: ../../config/sandbox-native.json
  • note frontmatter-key unknown frontmatter key "effort"

Process rating: all ten parameters 32/100

Will not run. References files that are not bundled: ../../../guide/security/sandbox-native.md, ../sandbox-status/SKILL.md, ../../config/sandbox-native.json
  • 0Tools and files. 3 referenced file(s) missing: ../../../guide/security/sandbox-native.md, ../sandbox-status/SKILL.md, ../../config/sandbox-native.json
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 75Steps. 3 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2108 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 331: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 3 items
  • +4Has examples (5 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.