Content
67%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, highly actionable workflow skill with a clear step sequence, concrete tooling, templates, and a quality checklist. Its main weakness is conciseness — repeated guardrails and a padded forbidden-phrase list — and the absence of any progressive-disclosure references for a moderately long single file.
Suggestions
Consolidate the repeated 'do not scrape GitHub Trending' and 'do not fabricate facts' guardrails into a single authoritative section and reference it, rather than restating them in Step 1, the workflow intro, and 失败和不确定情况.
Move the long forbidden-process-expression list and the article skeleton/template into a separate reference file (e.g. references/article-template.md) to shorten SKILL.md and improve progressive disclosure.
Add an explicit per-project validate→fix loop (e.g. after building each 事实卡, verify links and source claims before proceeding to the article) to strengthen workflow checkpoints for this batch operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and does not explain concepts Claude already knows, but several guardrails are repeated (the 'do not scrape GitHub Trending' instruction appears in Step 1, the workflow intro, and 失败和不确定情况; the '禁止把未验证信息写成事实' theme recurs across 数据来源 and DeepWiki sections) and the forbidden-phrase list is padded, so it could be tightened. | 3 / 5 |
Actionability | Provides concrete executable guidance — a file-name pattern (markdown/github-weekly-trending-YYYY-WW.md), named DeepWiki MCP tools (read_wiki_structure, read_wiki_contents, ask_question) with a concrete repoName example, README fallback URLs, a copy-paste article skeleton, and a Mermaid example — with only minor gaps in fully covering edge cases. | 4 / 5 |
Workflow Clarity | A clear 6-step sequence is backed by a workflow diagram, a 质量校验 checklist, and a 失败和不确定情况 error-handling section with explicit cross-validation (事实校验) at the end; validation is mostly a final gate rather than per-step validate→retry loops, leaving minor checkpoint gaps versus the top anchor. | 4 / 5 |
Progressive Disclosure | No bundle files exist, so all guidance lives in a single well-organized 326-line file with clear section headers and no nested/deep references; structure is good, though reference-like sections (图表规则, 竞品对比规则, 代码示例规则) are inlined and could optionally be split out. | 4 / 5 |
Total | 15 / 20 Passed |