FC hk-stock-monitor
港股+A股实时盯盘系统,支持技术分析、涨跌幅告警、飞书推送。使用场景:(1) 查询港股/A股实时行情,(2) 监控股票涨跌幅告警,(3) 生成技术分析报告,(4) 定时推送盯盘报告。触发关键词:盯盘、股票监控、港股行情、A股行情、涨跌告警、技术分析。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
- 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 · 4
-
critical Secrets in code
secret-openai-keyscripts/data-sources.js:15OpenAI-style API key (quoted — discussed, not commanded)qverisApiKey: process.env.QVERIS_API_KEY || 'sk-p…5Gs',
quoted -
critical Secrets in code
secret-openai-keyscripts/monitor.js:66OpenAI-style API key (quoted — discussed, not commanded)qverisApiKey: process.env.QVERIS_API_KEY || 'sk-p…5Gs',
quoted
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenscripts/data-sources.js:15High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)qverisApiKey: process.env.QVERIS_API_KEY || 'sk-p…5Gs',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/monitor.js:66High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)qverisApiKey: process.env.QVERIS_API_KEY || 'sk-p…5Gs',
quoted
Files scanned: 6. 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. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 359 tokens
- 100Running it twice. No mutating operations
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 125: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.