BF a-share-expert
A-share (China) stock trading decision expert. Integrates stock data MCP servers with expert methodology across 9 scenarios: holding diagnosis, candidate screening, event-driven analysis, portfolio optimization, intraday scanning, theme-launch hunting, and profit-taking/stop-loss discipline. For Shanghai/Shenzhen main-board trading decisions.
A-share (China) stock trading decision expert.
As a process F 40/100 · Will not run — References files that are not bundled: URL
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 · 0
✓ No critical or high findings
Files scanned: 9. 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 2, column 14: description: A-share (China) stock trading decision expert. Integrates stock da… ^ ); 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") - warning
missing-refreference to a missing file: URL
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: URL
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 97 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3689 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)
- +3Output format is not stated: the model decides each time
- -2219 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 344: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 97 items
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.