CF yufluentcn-seo-pro
>-
>-
As a process F 33/100 · Will not run — References files that are not bundled: ../../docs/技能-SEO关键词客户指南.md
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Exfiltration
net-credential-useREADME.md:20Credential used in a network call (verify the destination is the intended service)$env:TOKENAPI_BASE_URL = "http://loca…080/v1"
-
low Exfiltration
read-dotenvREADME.md:10Reads a .env filecopy .env.example .env
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 4, column 1: 跨境电商 SEO 关键词研究 — 亚马逊关键词+Backend、COSMO/Rufus 语义场景、Shopify 站内+Meta、TikTok 搜索+ 话题标签，经 Yufluent 云端 Harness 输出结构化投放建议。Cross-border ecommerce ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../../docs/技能-SEO关键词客户指南.md
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: ../../docs/技能-SEO关键词客户指南.md
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2231 tokens
- 100Running it twice. No mutating operations
- low 12 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)
- +3Description length 2: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -32 of 3 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 29 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 41.