BC generate-sandbox-policy
Generate sandbox security policies from plain-language requirements and optional REST API documentation. Produces L4 or fine-grained L7 network policies and ordered network middleware configuration. Use for API access rules, middleware host selection, failure behavior, or built-in and operator-run middleware attachment. Trigger keywords - generate policy, create policy, update policy, change policy, sandbox policy, network policy, API policy, security policy, allow API, restrict API, network middleware, supervisor middleware.
Generate sandbox security policies from plain-language requirements and optional REST API documentation.
As a process C 54/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9003 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 435): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 54/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 24 mutating operations with no state check
- 40Execution cost. Instruction body is 9003 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (read, web) that frontmatter does not declare
- 60Steps. 102 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100Failures and branches. 10 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
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)
- +1No license
- +2Single-language instructions
- +3Description length 531: enough signal without eating the budget
- +4Structure: 44 headings
- +3Step-by-step instructions: 102 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.