Content
73%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.
The content is highly actionable with executable, well-documented code and clearly sequenced quantitative workflows, but it is lengthy and monolithic — inlining tables, formulas, and code templates that would be better split into reference files for conciseness and progressive disclosure.
Suggestions
Move large reference material (data-analysis code templates in section 7, prompt-template library in section 8, and ratings/threshold tables) into separate files under references/ and replace them with concise summaries plus one-level-deep links.
Trim domain knowledge Claude already knows (basic definitions of LOF/分级基金, generic asset-allocation framing) to tighten conciseness.
Add explicit validation/checkpoint steps for data-dependent workflows (e.g. verify tushare API response is non-empty before computing tracking error) to strengthen workflow clarity for batch operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and assumes Claude's competence on most concepts, but at ~870 lines it contains large reference tables, ratings thresholds, and worked formulas that re-explain domain knowledge Claude already knows and could be trimmed or moved to references. | 3 / 5 |
Actionability | The skill provides multiple fully executable, copy-paste-ready Python functions (etf_score, fee_drag_analysis, calc_tracking_error, factor_exposure_analysis, tushare data loaders) with docstrings covering the common analytical cases. | 5 / 5 |
Workflow Clarity | Multi-step processes such as the 5-step ETF selection framework and rebalancing triggers are clearly sequenced with explicit thresholds, and quantitative scoring models provide implicit checkpoints; however, data-dependent batch/analysis workflows lack explicit validate-then-proceed feedback loops, so it falls just short of a 5. | 4 / 5 |
Progressive Disclosure | The body has clear section structure, but no bundle/reference files exist, so large blocks that belong in separate files (full data-analysis code templates, prompt-template library, ratings tables) are inlined in SKILL.md rather than split into one-level-deep references. | 3 / 5 |
Total | 15 / 20 Passed |