BC chan-stock-analysis
基于BARF框架的缠论多级别联立股票/指数/黄金行情分析。触发词：「使用缠论分析下」「分析下股票」「缠论分析」「帮我分析下」。优先级最高。必须获取日K+30分钟+5分钟+1分钟四级数据进行分析。采用akshare优先、futu备用的数据获取策略。多级别联动判断是核心要求。支持A股、港股、美股及黄金XAUUSD等走势分析。支持可视化绘图。
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 files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Obfuscation
uni-zero-widthREPORT_SAMPLE.md:11Zero-width / invisible characters (possible hidden text) (6 occurrences) (test fixture / example file)- **背驰分析**：价格在1.129创出新高，但下方MACD指标并未同步创出新高，DIFF值有走平回落迹象，红柱面积显著萎缩。这构成了 **“日线级别上涨动能衰竭信号”**␀ ，预示着本段上涨趋势已进入尾声，存在构筑大级别顶部的极大可能。当前属于上涨趋势背驰后的第一次回拉过程，正在寻找一个次级别（30分钟）的卖点。
fixture
Files scanned: 10. 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. 105 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1623 tokens
- 100Running it twice. No mutating operations
- low 11 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)
- +3Output format is not stated: the model decides each time
- -33 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 169: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 105 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.