Content
81%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 body is a highly actionable, well-sequenced instruction-only skill: concrete search strings, named sources, a fixed report template, validation checklist, and fallback handling for missing data. Its main weakness is redundancy — quality standards, special-case rules, and the final checklist repeat the same requirements — and the large inline report template that could be split into a reference file.
Suggestions
Merge '质量标准' and the '输出检查清单' into a single section (or make the checklist reference the standards) — the four-part 前提/推导/数据/崩塌 rule and the chart requirements are each stated twice.
Move the ~100-line '报告结构模板' into a references/report-template.md file and keep a short module-order summary in SKILL.md, improving both conciseness and progressive disclosure.
Fold the '数据不足时' bullet list into the search-strategy section of Step 1 where the data gap would actually be discovered, instead of a separate late section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient — the report template and premise-matrix format are the core deliverable and earn their lines — but there is measurable redundancy: '质量标准', '特殊场景处理/数据不足时', and the '输出检查清单' restate the same requirements two to three times (e.g. the Mermaid+matrix requirement and the '前提/推导/数据/崩塌' four-part rule each appear twice). It matches the 'mostly efficient but could be tightened' anchor rather than the minor-trim anchor above. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: exact search keyword strings ('"A股" OR "中国股市" 今日 开盘'), named sources to fetch (东方财富、同花顺、Bloomberg中文), a fill-in premise-matrix format, a fixed report module order, a concrete file-naming pattern ('市场开局分析_YYYYMMDD.md'), and an explicit fallback when live data is unavailable. Specific examples cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | A clearly sequenced workflow (Step 1 搜集信息 → Step 2 前提假设矩阵 → Step 3 生成报告 → Step 3.5 可选确认) with explicit validation checkpoints: the '输出检查清单' self-check before delivery, the '数据不足时' fallback loop, and the requirement that every cited datum carries source and time. It matches the anchor requiring explicit validation steps and checklists; the operations are non-destructive so no cap applies. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the single-file body is well-sectioned with clear headers and a fixed template, so navigation is easy. However, the ~100-line report structure template is inline content that could plausibly live in a references/ file, and there are no external references at all — good structure with minor organization gaps rather than the cleanly split ideal. | 4 / 5 |
Total | 17 / 20 Passed |