CD cloudq-intl
Use when the user asks about Tencent Cloud (INTERNATIONAL SITE), AWS, Alibaba Cloud, or other multi-cloud resources — architecture diagrams, architecture catalog and details, architecture assessment, drawing architecture diagrams, enabling Smart Advisor, AI-powered inspection, AI capacity monitoring, AI chaos drills, AI cloud diagnostics, proactive alerts, architecture health score, cloud O&M Q&A, cloud resource inventory, cloud cost optimization, security and compliance, resource inventory, idle resource checks, cloud product best practices, and other AIOps / ChatOps / CloudOps operations.
Use when the user asks about Tencent Cloud (INTERNATIONAL SITE), AWS, Alibaba Cloud, or other multi-cloud resources — architecture diagrams, architecture…
As a process D 47/100 · Unfinished process — References files that are not bundled: url
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
- The text references files that are not there: add them or drop the references.
- 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: Read Write Bash Grep
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: url - note
frontmatter-keyunknown frontmatter key "description_en"
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: url
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4150 tokens
- 85Steps. 16 steps, 1 vague phrases
- 100Failures and branches. 3 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
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
- -220 emoji in the instructions: noise for the model
- -33 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 597: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.