mootdx

Mootdx A-share market data via TCP-direct 通达信 servers. Free, no API key, no IP rate limits. Use as the stable A-share OHLCV fallback when akshare's East Money scrape is throttled.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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.

A well-structured, highly actionable single-file reference with executable code and thorough limitation tables. It loses points only for inlined version-sensitive details and reference bulk that could be split out, plus a missing data-validation checkpoint.

Suggestions

Add an explicit validation checkpoint after fetching (e.g. 'If the DataFrame is empty, fall back to tushare/akshare per the chain') to close the workflow gap for BJ/extended-market empty returns.

Move the frequency-code and Key Methods reference tables into a one-level-deep REFERENCE.md and link to it from the body, keeping SKILL.md as a lean overview.

Isolate time-sensitive version pins (httpx<0.26 workaround, v0.11.7 upstream issue) into a clearly labeled 'Version notes / known upstream issues' section so they don't penalize conciseness.

Dimension	Reasoning	Score
Conciseness	Dense and largely lean with no padding of concepts Claude already knows, but embeds time-sensitive version numbers ('httpx<0.26', 'v0.11.7', 'httpx>=0.28.1') outside any deprecated/old-patterns section, which the rubric penalizes.	4 / 5
Actionability	Copy-paste-ready Quick Start code with concrete symbols and dates, plus complete tables for frequency codes, methods, and symbol formats covering the common cases.	5 / 5
Workflow Clarity	The fetch sequence is unambiguous and edge cases are documented in the Known Limitations table, but there is no explicit validation checkpoint (e.g. 'verify the returned DataFrame is non-empty') despite known empty-return cases for BJ/extended markets.	4 / 5
Progressive Disclosure	Well-organized into clear sections with external doc links, but it is a single ~85-line reference file with no bundle files; the method/frequency reference bulk could be split into a one-level-deep reference file rather than inlined.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

A tight, third-person description that states a clear niche, concrete technical specifics, and an explicit use-trigger. It is distinctive and low-conflict; only slightly broader trigger-term coverage would push it higher.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete technical specifics ('A-share market data via TCP-direct 通达信 servers', 'OHLCV fallback') with several specific attributes (no API key, no IP rate limits); stops just short of enumerating multiple discrete actions, so not a 5.	4 / 5
Completeness	Explicitly answers both what ('Mootdx A-share market data via TCP-direct 通达信 servers') and when ('Use as the stable A-share OHLCV fallback when akshare's East Money scrape is throttled') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Good coverage of niche-natural terms a user would say ('A-share', 'OHLCV', 'akshare', 'East Money', 'throttled'), though a few common variations (e.g. '通达信', 'TDX', 'rate-limited') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear narrow niche (TDX-protocol A-share data) with a distinct trigger tied to akshare throttling, making conflict with other data-source skills minimal.	5 / 5
	Total	18 / 20 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/mootdx/SKILL.md
Commit: d71ed8d

Reviewed: 4 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.