BD FTShare-market-data
非凸科技金融数据技能集。覆盖 A 股股票列表、行情、IPO、大宗交易、融资融券、单股行情估值、可转债、ETF、基金、指数（含分页指数描述、下载描述 PDF、权重汇总/成份明细、下载权重 xlsx、详情/K 线/分时）、宏观经济，以及港股公司介绍/估值分析/基础视图/K线、东财美股列表/历史K线/最新行情、native 美股基础信息/利润表/现金流量表/资产负债表、港股财报三表(利润/现金流/资产负债)/东财港股指数日K线等接口（market.ft.tech / ftai.chat）。用户询问 A 股、港股、美股的代码、行情、估值、K线、指数权重/描述、新闻与宏观数据时使用。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 11238 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 43/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
- 40Execution cost. Instruction body is 11238 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 187 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 32 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (39 tags): a typed call is more reliable
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 290: enough signal without eating the budget
- +4Structure: 80 headings
- +3Step-by-step instructions: 187 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.