BF literature-reviewer-skill
根据用户提供的论文主题,进行系统性中英文文献回顾(Literature Survey)。 采用8阶段工作流,支持CNKI、Web of Science、ScienceDirect等主流数据库, 无需API配置,通过浏览器自动化获取文献信息。 输出包含GB/T 7714-2015引文、标题、摘要的Markdown文档。 当用户提到"文献回顾"、"文献综述"、"帮我找文献"、"中英文文献搜索"、"写综述"等关键词时触发。 NOTE: The 'examples/' folder contains sample outputs and is not included in skill installation.
根据用户提供的论文主题,进行系统性中英文文献回顾(Literature Survey)。 采用8阶段工作流,支持CNKI、Web of Science、ScienceDirect等主流数据库, 无需API配置,通过浏览器自动化获取文献信息。 输出包含GB/T…
As a process F 36/100 · Will not run — References files that are not bundled: url
The same skill appears in 1 more place: openclaw-master-skills
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: url
Process rating: all ten parameters 36/100
- 0Tools and files. 1 referenced file(s) missing: url
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4416 tokens
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 17 top-level sections: this looks like several domains in one skill
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
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -34 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 307: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.