CF architecture-inventory-risk-assessment
Inventory your cloud architectures and assess risks. Query architecture blueprints, evaluate Well-Architected scores, and identify governance gaps.
As a process F 33/100 · Will not run — References files that are not bundled: {免密登录链接}, 免密登录URL, references/plugins/
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 files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 9
✓ No critical or high findings
Medium and low: 9
-
medium Obfuscation
obf-base64-blobadvisor-2020-07-21/云架构控制台相关接口/开启智能顾问授权.md:84Long base64-looking blob* Tencent Cloud SDK 3.0 for Java: [GitHub](https://github.com/TencentCloud/tencentcloud-sdk-java/blob/master/src/main/java/com/tencentcloudapi/advisor/v20200721/AdvisorClient.java), [Gitee](https://gi
-
medium Dangerous commands
cmd-shell-rcREADME.md:22Writes to a shell startup fileecho 'export TENCENTCLOUD_SECRET_ID="your-secret-id"' >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcREADME.md:23Writes to a shell startup fileecho 'export TENCENTCLOUD_SECRET_KEY="your-secret-key"' >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:28Writes to a shell startup fileecho 'export TENCENTCLOUD_SECRET_ID="your-secret-id"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:29Writes to a shell startup fileecho 'export TENCENTCLOUD_SECRET_KEY="your-secret-key"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:93Writes to a shell startup fileecho 'export TENCENTCLOUD_ROLE_NAME="advisor"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:104Writes to a shell startup fileecho 'export TENCENTCLOUD_ROLE_ARN="qcs::cam::uin/1000…ame/advisor"' >> ~/.bashrc
-
low Dangerous commands
cmd-shell-rccheck_env.py:261Writes to a shell startup file (string literal in code, not executed)log_info(' echo \'export TENCENTCLOUD_SECRET_ID="your-secret-id"\' >> ~/.bashrc')code literal -
low Dangerous commands
cmd-shell-rccheck_env.py:262Writes to a shell startup file (string literal in code, not executed)log_info(' echo \'export TENCENTCLOUD_SECRET_KEY="your-secret-key"\' >> ~/.bashrc')code literal
Files scanned: 35. 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
missing-refreference to a missing file: {免密登录链接} - warning
missing-refreference to a missing file: 免密登录URL - warning
missing-refreference to a missing file: references/plugins/
Process rating: all ten parameters 33/100
- 0Tools and files. 3 referenced file(s) missing: {免密登录链接}, 免密登录URL, references/plugins/
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 13 mutating operations with no state check
- 100Steps. 68 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3514 tokens
- low 10 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +3Description length 147: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 68 items
- +4Has examples (24 code blocks)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.