BD crypto-scope
加密货币数据分析助手，实时价格查询、技术指标分析、交易信号生成。使用场景：(1) 实时价格监控 (2) 技术指标分析（MA/RSI/MACD） (3) 交易信号生成 (4) 市场趋势判断。Triggers: "加密货币", "比特币", "以太坊", "价格分析", "技术指标", "交易信号", "crypto", "bitcoin", "eth"。
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Secrets in code
secret-labelled-tokenscripts/configure_skillpay.sh:13Labelled token / key literal (vendor format unknown — verify it is not a live credential)API_KEY="sk_0…971"
-
low Secrets in code
secret-password-literalscripts/configure_skillpay.sh:13Hard-coded password / key literal (may be an example)API_KEY="sk_0…971"
Files scanned: 10. 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: Nested mappings are not allowed in compact mappings at line 3, column 14: description: 加密货币数据分析助手，实时价格查询、技术指标分析、交易信号生成。使用场景：(1) 实时价格监控 (2) 技术指标分析（MA/RSI/… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 61 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1666 tokens
- 100Running it twice. No mutating operations
- low 14 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- -33 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 177: enough signal without eating the budget
- +4Structure: 45 headings
- +3Step-by-step instructions: 61 items
- +4Has examples (24 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.