Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An excellent single-file reference: executable Quick Start, precise tables for frequency codes, methods, symbol formats, and a candid Known Limitations section with workarounds. The main deductions are inline version/date-sensitive notes and the absence of an explicit data sanity-check step.
Suggestions
Move version-sensitive details (the httpx<0.26 pin workaround, the v0.11.7 extended-market note) into a dedicated 'Version notes / old patterns' section so they don't age the whole document.
Add a brief validation step after fetching (e.g., check the returned DataFrame is non-empty and covers the requested date range, falling back to the next source in the chain) to close the workflow-clarity gap.
Consider extracting the Key Methods / frequency-code tables into a references/ file if the skill grows, keeping SKILL.md as a leaner overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and reference-style with no concept-explanation padding (frequency-code table, symbol prefix rules, quirks like 'duplicate volume alongside the legacy vol'). However, version-sensitive info appears inline ('pins httpx<0.26', 'as of v0.11.7', 'httpx>=0.28.1') outside any old-patterns/deprecated section, which the guidelines penalize, so not anchor 5. | 4 / 5 |
Actionability | Quick Start is copy-paste executable and covers the common cases (daily get_k_data with date range plus intraday bars with offset), backed by a concrete install command, full return-column schemas, and symbol auto-detection rules. The only illustrative snippet (run(strategy=..., source="mootdx")) is a deliberate override example, not a gap. | 5 / 5 |
Workflow Clarity | Single-purpose skill with an unambiguous usage path, a documented fallback chain ([tushare, mootdx, akshare]), and failure-mode handling (BJ get_k_data raises KeyError → loader warns and skips). No explicit data-validation checkpoint (e.g., verify the returned frame is non-empty before use), so it sits at anchor 4 rather than 5. | 4 / 5 |
Progressive Disclosure | A single ~87-line file, cleanly sectioned, with all content appropriately inline for a compact data-source cheat-sheet and external docs linked one level deep. No bundle files exist and the body exceeds the ~50-line simple-skill threshold, so the top anchor's 'content appropriately split' is not fully demonstrated. | 4 / 5 |
Total | 17 / 20 Passed |