BF zhihu-research-page
通过大规模联网搜索自动创建知乎风格的深度知识网页,样式高度还原 zhihu.com。生成 10 个章节的多答主模拟回答页面,含 ≥10 万有效中文字和 ≥500 次真实搜索引用。支持手动裁剪为任意比例版本(如"执行 5% 版本"→ ≥5 千字 / ≥25 次搜索),多次执行自动创建带版本号的独立文件夹。适用于生成知识专题页、学习路径教程、产品深度百科、行业研究报告等需要系统整理某一主题知识的场景。
通过大规模联网搜索自动创建知乎风格的深度知识网页,样式高度还原 zhihu.com。生成 10 个章节的多答主模拟回答页面,含 ≥10 万有效中文字和 ≥500 次真实搜索引用。支持手动裁剪为任意比例版本(如"执行 5% 版本"→ ≥5 千字 / ≥25…
As a process F 31/100 · Will not run — References files that are not bundled: references/css-template.css
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit map keys need to be followed by map values at line 6, column 1: description: 通过大规模联网搜索自动创建知乎风格的深度知识网页,样式高度还原 zhihu.com。生成 10 个章节的多答主模拟回答页面,含 ≥1… **[重要]100%版本约需 100 分钟且token消耗巨大,建议先生成 2% 版本检验效果** type: "agent" ^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 200 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
body-longSKILL.md body ≈ 7047 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/css-template.css - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "invocation" - note
frontmatter-keyunknown frontmatter key "difficulty" - note
frontmatter-keyunknown frontmatter key "claude_version" - note
frontmatter-keyunknown frontmatter key "permissions" - note
frontmatter-keyunknown frontmatter key "examples"
Process rating: all ten parameters 31/100
- 0Tools and files. 1 referenced file(s) missing: references/css-template.css
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (zhihu-research-page) differs from the folder (zhihu-research-page-skill)
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 7047 tokens
- 100Steps. 139 steps
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (18 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -219 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 62 headings
- +3Step-by-step instructions: 139 items
- +4Has examples (25 code blocks)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 39.