CtrlK
BlogDocsLog inGet started
Tessl Logo

tushare

tushare是一个财经数据接口包,拥有丰富的数据内容,如股票、基金、期货、数字货币等行情数据,公司财务、基金经理等基本面数据。该模块通过标准化API方式统一了数据资产的对外服务方式,以帮助有需要的技术用户更实时、简洁、轻量的使用相关数据。

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./a_全网优秀资源/10_大模型/07_skill包/vibe_trading_skills/tushare/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured data-source skill: an executable quick start, concrete parameter conventions, and an excellent one-level-deep reference system where every one of ~200 interface docs exists and is organized by category. Its main weakness is token efficiency — a verbatim-duplicated overview section and a verbose description column that repeats content already present in the linked reference files — plus the absence of error-handling guidance for API limits.

Suggestions

Remove or shrink the 概述 section, which repeats the frontmatter description word-for-word and adds no new information.

Drop or drastically shorten the 描述 column in the interface table (or keep only the interface name/category); each linked reference file already contains the full description, parameters, and usage notes.

Add a brief error-handling note to 快速上手 covering token validation failure and the per-request row caps (e.g., 100/200/6000 rows) with the multi-request-by-date pattern, since the table mentions these limits but the workflow never tells the agent how to respond to them.

DimensionReasoningScore

Conciseness

The quick start and parameter sections are lean with no explanation of concepts Claude already knows, but the 概述 section duplicates the frontmatter description verbatim, and the ~230-row interface table's 描述 column repeats operational notes ('数据由Tushare社区自产…可以联系管理员评估', '建议在每日19点后提取') that already live in each linked reference file. This fits anchor 3 (mostly efficient but could be tightened) — not 2 because the bulk is a navigational index rather than padded prose, not 4 because the duplicated overview and verbose table column are noticeable inefficiencies.

3 / 5

Actionability

The body gives fully executable, copy-paste-ready guidance: 'pip install tushare -i https://pypi.tuna.tsinghua.edu.cn/simple', 'export TUSHARE_TOKEN=your_token', and a complete Python example with token fallback ('token = os.getenv(\'TUSHARE_TOKEN\') or ts.get_token()') plus a concrete query (pro.stock_basic with fields). Concrete parameter formats (YYYYMMDD, ts_code like 000001.SZ, pandas DataFrame return) and two runnable example scripts cover the common cases — matching anchor 5.

5 / 5

Workflow Clarity

快速上手 presents a clear ordered sequence — install, register/token, locate the interface in the docs, query with code — each with a concrete command or link. However, there are no validation/error checkpoints (e.g., verifying the token works, handling the 100/200-row-per-request caps or rate limits that the table itself mentions). This fits anchor 4 (clear sequence, minor validation gaps): above 3 because the sequence is concrete and complete, below 5 because no verification or error-recovery feedback loop is described.

4 / 5

Progressive Disclosure

The SKILL.md body is a true overview (quick start, parameter formats, script links) with per-interface detail pushed exactly one level deep into references/ organized by category directories matching the 分类 column — all 196 uniquely referenced files (e.g. references/股票数据/基础数据/股票列表.md, which contains the full input/output parameter tables) were verified to exist on disk, and the example scripts exist under scripts/. This matches anchor 5 (clear overview, well-signaled one-level-deep references, easy navigation).

5 / 5

Total

17

/

20

Passed

Description

56%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the product and its data domain (Chinese financial market data: stocks, funds, futures, crypto, financials), but describes it in marketing language rather than concrete actions, and entirely lacks 'when to use' trigger guidance. It is serviceable but reads like a product blurb rather than a skill description optimized for invocation.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs Chinese financial market data (股票、基金、期货、期权、港股、美股、宏观数据) via the tushare API or mentions tushare, A股, 行情, or 财报.'

Replace the buzzword sentence '该模块通过标准化API方式统一了数据资产的对外服务方式' with concrete actions such as '获取股票/基金/期货/期权的行情、财务、基本面数据,返回pandas DataFrame'.

Include missing natural trigger terms like A股、港股、美股、交易日历 and the return format (pandas DataFrame) to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain and enumerates data types ("股票、基金、期货、数字货币等行情数据,公司财务、基金经理等基本面数据"), but the only action phrasing is the generic, buzzword-heavy "通过标准化API方式统一了数据资产的对外服务方式" — no concrete action such as fetching quotes or financial statements is stated. This matches anchor 2 (names the domain, actions minimal or generic): it is not 3 because no concrete action verb like '获取/查询' appears, and not 1 because the domain and data categories are specifically named rather than entirely vague.

2 / 5

Completeness

The 'what' is clearly stated (a financial data interface package covering stocks, funds, futures, crypto quotes and fundamentals), but there is no 'Use when…' clause or any equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not 2 because the 'what' is concrete, not vague, and not merely a 'when' without a 'what'.

3 / 5

Trigger Term Quality

It includes natural domain keywords users would say ("股票", "基金", "期货", "数字货币", "行情数据", "公司财务", "基金经理") plus the product name 'tushare'. A few common natural terms are missing (A股, 港股, 美股, 交易日历, 财报), so it fits anchor 4 (good keyword coverage, a few natural terms missing) rather than 5 (comprehensive synonyms/extensions).

4 / 5

Distinctiveness Conflict Risk

The brand name 'tushare' plus the Chinese financial-market data API niche makes it mostly distinct with minimal conflict risk. It is not 5 because '财经数据' (financial data) is a broad trigger that could overlap with other finance-data skills, and no explicit use-when clause disambiguates; it is clearly above 3 since the named product and specific asset classes anchor it to a clear niche.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 33 missing, 229 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

13

/

16

Passed

Repository
charliedream1/ai_quant_trade
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.