Content
78%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.
A well-structured instruction-only skill: a tight six-step workflow, sensible output standards, and a clean one-level reference split that keeps the body short. The main weaknesses are duplicated source guidance between the body and the reference file, and the absence of an explicit pre-write validation checkpoint for source coverage.
Suggestions
De-duplicate the evidence-source lists: keep only one or two primary-source pointers in the body and let references/report-framework.md's Source Standards section carry the full list.
Add an explicit validation step before writing the report, e.g. "Before writing, verify every precise market-size, market-share, or financial figure has a source link; drop or hedge any that do not."
Make evidence gathering more actionable by specifying a concrete search pattern (e.g., company annual report / 10-K site + industry association statistics) rather than the generic "Browse current authoritative sources".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence with no concept explanations, but the "Gather current evidence" source list ("annual reports, 10-K/20-F, prospectuses, official investor relations pages, exchange filings, and regulator filings") substantially duplicates the Source Standards section already in references/report-framework.md. That trimmable duplication keeps it just below the every-token-earns-its-place anchor, and well above the noticeably-verbose level. | 4 / 5 |
Actionability | Guidance is mostly executable for an instruction-only skill: a concrete save path ("markdown/"), an example filename ("markdown/半导体产业链投行视角分析.md"), named visual types, and specific analysis dimensions. "Browse current authoritative sources" remains high-level without a concrete search or verification routine, which is the minor gap separating it from fully actionable. | 4 / 5 |
Workflow Clarity | The six numbered steps are clearly sequenced (scope → evidence → chain map → company selection → analysis → write file) and include a fallback ("If evidence is insufficient, say what is missing and write a narrower report"). There is no explicit validation checkpoint before writing (e.g., confirming every precise number has a source), so it fits clear-sequence-with-minor-validation-gaps rather than the explicit-checkpoint anchor at 5. | 4 / 5 |
Progressive Disclosure | The body is a well-organized overview that points to exactly one real, verified reference (references/report-framework.md, 171 lines) with a clear statement of what it covers, one level deep and clearly signaled. This matches the clear-overview anchor; no content that belongs in a separate file is inlined. | 5 / 5 |
Total | 17 / 20 Passed |