Content
77%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured instruction-only skill with a clear sequenced workflow and explicit validation/quality-gate checkpoints. Its main weakness is actionability: per-asset guidance is directional checklist advice without concrete examples or templates, and everything lives in one inline file with no progressive disclosure.
Suggestions
Add one concrete example per asset type — e.g. a sample use-of-funds table layout or a one-pager section template — to lift actionability from directional to copy-paste-ready.
Split detailed per-asset guidance (pitch deck flow, financial model spec) into reference files under references/ and link to them from a leaner overview, improving progressive disclosure for this multi-asset skill.
Make the Quality Gate an explicit pass/fail step tied back to step 5 of the Core Workflow so the validation feedback loop is unambiguous rather than a separate checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — bullet-list guidance with no padded prose and no explanations of concepts Claude already knows (e.g. it never defines what a pitch deck is); the minor overlap between the Golden Rule source list and Core Workflow step 1 is not enough to drop it below the lean/efficient anchor. | 3 / 3 |
Actionability | It gives concrete structural guidance — the 12-step "建议流程" deck flow and per-asset checklists — but the directives are largely directional ("用一句简洁的话说明公司业务", "尽早展示牵引力") without examples or templates, so it stops at "some concrete guidance but incomplete / missing key details." | 2 / 3 |
Workflow Clarity | A clear 5-step Core Workflow is paired with explicit validation — step 5 "根据单一事实来源交叉检查每个数据", the conflict-resolution feedback loop "如果出现数据冲突，请在起草前先予以解决", and a pre-delivery Quality Gate checklist — matching the anchor for a clear sequence with explicit validation and feedback loops. | 3 / 3 |
Progressive Disclosure | The single SKILL.md is well-sectioned and has no deep reference nesting (so not a 1), but at ~90 lines across multiple asset types all guidance is inline with no progressive disclosure to separate reference files and no bundle files, fitting "some structure but content that should be separate is inline." | 2 / 3 |
Total | 10 / 12 Passed |