BB gcp-networking-optimizer
Identify and reduce GCP networking and egress costs across projects and regions
As a process B 72/100 · Nearly there — weak spots: consistency, running it twice, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 0
✓ No critical or high findings
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") - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pack" - note
frontmatter-keyunknown frontmatter key "tier" - note
frontmatter-keyunknown frontmatter key "price" - note
frontmatter-keyunknown frontmatter key "permissions" - note
frontmatter-keyunknown frontmatter key "credentials"
Process rating: all ten parameters 72/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (gcp-networking-optimizer) differs from the folder (networking-optimizer)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 767 tokens
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 79: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
This instruction-only skill is coherent with its stated purpose and uses user-provided, read-only GCP billing and networking data without asking for credentials.
LLM: benign (high) · VirusTotal: · 29 May 2026