akshare

AKShare financial data aggregator (18k+ stars). Free, no API key. Covers A-shares, US, HK, futures, macro, forex. Primary fallback for tushare and yfinance.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

The body is lean, highly actionable, and well-organized for a single-purpose data-source skill, with executable examples and useful reference tables. Its one weakness is progressive disclosure: it points to a references/ subdirectory that is not actually present.

Suggestions

Either create the referenced `references/` subdirectory with the promised 'less common interfaces' docs, or remove the dangling reference and note that the official docs at the linked URL cover uncommon interfaces.

De-duplicate the 'free / no API key' and '18k+ stars' facts already in the frontmatter to tighten the Overview further.

Consider moving the full function tables (Top 10 Interfaces, Column Names) into a reference file and keeping SKILL.md as a tighter overview, which would realize the progressive-disclosure structure the body already implies.

Dimension	Reasoning	Score
Conciseness	The body is lean and reference-style — tight code blocks, compact tables for interfaces and column names, and a three-sentence overview — assuming Claude's competence without explaining basic concepts, matching anchor 3; minor duplication of 'free/no API key' and '18k+ stars' from the frontmatter is not enough to drop to anchor 2.	3 / 3
Actionability	Quick Start gives fully executable `import akshare as ak` calls with concrete symbols, periods, and date ranges, plus explicit symbol/date format specs and a Chinese-to-English column mapping table — copy-paste ready, matching anchor 3 rather than the pseudocode of anchor 2.	3 / 3
Workflow Clarity	This is a single-purpose data-fetch skill with no multi-step or destructive operation, and the Quick Start shows the unambiguous sequence (import -> call with params) that the rubric allows to score 3 for simple skills; no validation checkpoint is required for a read-only fetch, so it is not capped at anchor 2.	3 / 3
Progressive Disclosure	Sections are well organized and easy to navigate, but the only external reference ('see the `references/` subdirectory') points to a directory that does not exist, so the progressive-disclosure structure is not actually realized with real one-level-deep files; this matches anchor 2's 'references present but not clearly signaled / could be better organized' rather than anchor 3's confirmed split.	2 / 3
	Total	11 / 12 Passed

Description

72%

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 conveys the skill's niche and includes strong natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, leaving the invocation condition only implied and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when fetching free A-share, US, HK, futures, macro, or forex market data, or as a fallback when tushare/yfinance are unavailable.'

Replace passive coverage language with concrete actions, e.g. 'Fetch OHLCV bars, real-time quotes, and macro/forex/futures series' to lift specificity toward anchor 3.

Drop non-trigger padding like '(18k+ stars)' from the description to keep it focused on capability and invocation.

Dimension	Reasoning	Score
Specificity	Quotes 'financial data aggregator', 'Covers A-shares, US, HK, futures, macro, forex', and 'Primary fallback for tushare and yfinance' name the domain and several data areas, but they describe coverage rather than listing multiple concrete action verbs, matching anchor 2; not anchor 1 (clearly more than vague) nor anchor 3 (no enumerated concrete actions).	2 / 3
Completeness	It states what the skill covers ('Covers A-shares, US, HK, futures, macro, forex') but the 'when' is only implied via 'Primary fallback for tushare and yfinance' with no explicit 'Use when...' trigger clause; per the judging guideline a missing explicit trigger caps completeness at 2, so not anchor 3 and clearly above anchor 1.	2 / 3
Trigger Term Quality	Natural domain terms a user would say are well covered — 'A-shares', 'US', 'HK', 'futures', 'macro', 'forex', 'tushare', 'yfinance' — matching anchor 3's 'good coverage of natural terms'; not anchor 2 because the core vocabulary is comprehensive rather than partial.	3 / 3
Distinctiveness Conflict Risk	The named library 'AKShare' plus specific market triggers ('A-shares', 'forex', 'futures') and explicit fallback role for tushare/yfinance carve a clear niche unlikely to conflict with other skills, matching anchor 3.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/akshare/SKILL.md
Commit: 8643fcd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.