BC stock-ocr
从通达信金融终端窗口截取股票日K图,并使用OCR识别MA均线数值。当用户需要获取股票MA均线数值、分析均线支撑压力位、或需要对交易软件截图进行文字识别时使用此skill。触发词:MA、均线数值、截图识别、股票技术指标、通达信金融终端。
As a process C 53/100 · Has gaps — 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 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.
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 · 7
✓ No critical or high findings
Medium and low: 7
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:148Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File scripts/conf…ps1 -ApiKey "your_api_key" -SecretKey "your_secret_key"
-
medium Secrets in code
secret-labelled-tokenSKILL.md:159Labelled token / key literal (vendor format unknown — verify it is not a live credential)- API Key: `dNJc…aPG`
-
low Secrets in code
secret-high-entropy-tokencapture_ma20.py:151High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)boundary = '----…0gW'
quoted -
low Secrets in code
secret-high-entropy-tokendebug_ocr.py:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)os.environ['BAIDU_SECRET_KEY'] = 'X989…3cA'
quoted -
low Secrets in code
secret-high-entropy-tokenma20_v2.py:261High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)boundary = '----…0gW'
quoted -
low Secrets in code
secret-high-entropy-tokenma20_v3.py:145High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)boundary = '----…0gW'
quoted -
low Secrets in code
secret-high-entropy-tokentest_baidu_ocr.py:10High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)os.environ['BAIDU_SECRET_KEY'] = 'X989…3cA'
fixturequoted
Files scanned: 28. 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")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1382 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 117: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -230 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.