BF stock-scanner
跨市场股票技术指标扫描系统。数据来源 TradingView,支持 A股/港股/美股/日股。 从用户 Obsidian vault 中的 watchlist 读取 ticker 列表,运行14项技术信号扫描 (MA交叉、RSI、MACD、BOLL、放量突破、缩量回调、量价背离、周K共振、综合评分等), 并将扫描报告(Markdown + 可选 Excel)保存回 Obsidian vault。 设计为每日定时运行。 当用户提到"股票扫描"、"技术指标扫描"、"stock scanner"、"run the scanner"、 "跑一下扫描"、"技术分析日报"、"watchlist scan"、"每日扫描"时触发本 skill。 也适用于用户要求对 watchlist 做批量技术分析、生成技术信号报告、或提到 TradingView 数据扫描等场景。
As a process F 31/100 · Will not run — References files that are not bundled: scripts/scanner.py
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-cron-mentionSKILL.md:66Mentions editing / listing crontab (documentation of a security skill)# crontab -e
security skill
Files scanned: 4. 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: scripts/scanner.py
Process rating: all ten parameters 31/100
- 0Tools and files. 1 referenced file(s) missing: scripts/scanner.py
- 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
- 40Consistency. Frontmatter name (stock-scanner) differs from the folder (tradingviewscanner)
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 552 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 379: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.