CD gcp-global-search
Query Google Cloud (谷歌云) product information, documentation, parameters, features, and pricing from official sources without login. Use when the user asks about Google Cloud products (Compute Engine, Cloud Storage, BigQuery, Cloud SQL, etc.), needs product documentation, wants to compare product specifications, or needs help finding specific product parameters and features.
Query Google Cloud (谷歌云) product information, documentation, parameters, features, and pricing from official sources without login.
As a process D 47/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:243Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Virus Total | Virus Total | 恶意软件分析服务 / Malware analysis service |
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6761 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 47/100
- 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
- 30Running it twice. 6 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 6761 tokens
- 85Steps. 52 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 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)
- +3Output format is not stated: the model decides each time
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 376: enough signal without eating the budget
- +4Structure: 43 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.