CB setup-deploy
Configure deployment settings for /land-and-deploy.
Sets up deployment parameters for /land-and-deploy. Promises configuration, but there's only one file—looks like instructions rather than a full workflow. Code quality scores 55: one medium-severity finding, not critical. Safety is solid at 95. No actual model runs or sandbox tests. Supports most platforms from Claude to DeepSeek.
Install it if you already know what your config needs. For deployment newcomers, this won't cut it: no execution examples, no result validation. Works as a reference, not an assistant.
Configure deployment settings for /land-and-deploy.
As a process B 75/100 · Nearly there — weak spots: inputs and preconditions, execution cost
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Write Edit Glob Grep AskUserQuestion
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 10898 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "preamble-tier" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 75/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 10898 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 103 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Failures and branches. 11 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 22 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (9 tags): a typed call is more reliable
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)
- +3Description length 51: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 41 headings
- +3Step-by-step instructions: 103 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.