Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body provides solid, executable CLI/API/config examples (strong actionability) but functions as a project README padded with marketing and project-metadata sections, lacks any validation/verification step for its batch fetching, and references files that are not bundled.
Suggestions
Trim README-style sections (architecture ASCII diagram, emoji feature list, 性能指标 table, 开发计划, 贡献指南, 许可证, 联系方式) that do not guide skill execution.
Add a brief validation/verification step for batch fetches, e.g. checking the output report for empty results or failed sources and retrying/reporting failures.
Either bundle the referenced config/ and src/parsers/ files (references/ or scripts/) with clearly signaled links, or remove the dangling references so the skill is self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The actionable core (CLI/API/config examples) is concise, but the body is padded with README-style sections (ASCII architecture diagram, emoji feature bullets, industry source counts, performance marketing table, 开发计划/贡献指南/许可证/联系方式) that do not help Claude execute the skill. Not anchor 1 because it does not explain basic concepts Claude already knows, but the padding keeps it from 3. | 2 / 3 |
Actionability | Provides copy-paste-ready CLI commands ("common-fetcher --industry coal --output daily.md"), a concrete Node.js API example with options, and an OpenClaw config snippet. Matches anchor 3 (fully executable commands/code, specific examples). The parser stub is incomplete but the primary usage paths are executable. | 3 / 3 |
Workflow Clarity | Usage is shown as single commands with no sequenced workflow, and a batch operation (fetching/processing many articles across 207 sources) has no validation or verification step (e.g., checking output, handling parse failures), which per the guideline caps workflow clarity at 2. Matches anchor 2 (steps/usage present but checkpoints missing). | 2 / 3 |
Progressive Disclosure | No bundle files exist (references/scripts/assets absent), yet the body references config/, src/parsers/, and *-sources.json that are not provided; everything is inline in one ~180-line file. README-like sections (architecture, performance, dev plan, contributing, license) are content that should be separate or removed. Matches anchor 2 (some structure, references not clearly signaled, content that should be separate is inline). | 2 / 3 |
Total | 9 / 12 Passed |