BD tickdb-market-data
TickDB 统一实时行情数据 API。使用此 skill 获取外汇、贵金属、指数、美股、港股、A股、加密货币的实时和历史行情数据。 触发场景： - 实时行情查询（"BTC现在多少钱"、"黄金价格"、"特斯拉股价"、"美元兑日元汇率"） - K线与技术分析（"帮我查K线"、"BTC小时线"、"AAPL日K"、"画个蜡烛图"） - 市场深度与成交（"买卖盘"、"订单簿"、"最近成交记录"） - 股票基本面（"腾讯市值多少"、"苹果市盈率"、"茅台股息率"、"公司信息"） - 资金流向（"主力资金流入"、"大单流向"、"北向资金"） - 市场指标（"换手率"、"振幅"、"量比"、"年初至今涨幅"） - 分时走势（"今天分时图"、"当日走势"、"盘中分钟数据"） - 产品搜索（"支持哪些币种"、"有哪些港股"、"能查什么外汇"） - API Key 相关（"API Key怎么申请"、"在哪里注册"、"怎么获取key"、"我没有key"） - 用户返回401或1001错误时，提示检查或重新申请API Key 常用查询快捷入口： - 📈 实时价格：BTCUSDT / XAUUSD / AAPL.US / 700.HK / 000001.SZ - 📊 K线数据：任意品种 + 周期（1m/5m/15m/1h/4h/1d/1w） - 💰 资金流向：港股/美股/A股个股资金流入流出 - 📋 股票信息：美股/港股/A股基本面数据
TickDB 统一实时行情数据 API。使用此 skill 获取外汇、贵金属、指数、美股、港股、A股、加密货币的实时和历史行情数据。 触发场景： - 实时行情查询（"BTC现在多少钱"、"黄金价格"、"特斯拉股价"、"美元兑日元汇率"） -…
As a process D 44/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.
- 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 Secrets in code
secret-high-entropy-tokenSKILL.md:813High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"apiKey": "Zols…qPy"
quoted
Files scanned: 2. 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") - note
frontmatter-keyunknown frontmatter key "api_key" - note
frontmatter-keyunknown frontmatter key "api_key_type" - note
frontmatter-keyunknown frontmatter key "api_key_obtained_at"
Process rating: all ten parameters 44/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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Execution cost. Instruction body is 4443 tokens
- 100Steps. 70 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 26 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
- +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
- +5Description quotes 16 example trigger phrases
- +3Description length 618: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 70 items
- +4Has examples (33 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.