AF paper-research-agent
Autonomous multi-agent paper research system. When user wants to research a topic, find related papers, or analyze academic literature, use this skill to orchestrate the full pipeline: intelligent search → PDF download → parallel agent analysis → comprehensive report generation. Triggers on: "research papers on X", "find related literature", "analyze papers", "调研论文", "查找相关文献", "分析论文", "帮我调研XXX领域"
As a process F 59/100 · Will not run — References files that are not bundled: scripts/research_probe.py, scripts/paper_downloader.py, scripts/agent_task_generator.py
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/research_probe.py - warning
missing-refreference to a missing file: scripts/paper_downloader.py - warning
missing-refreference to a missing file: scripts/agent_task_generator.py
Process rating: all ten parameters 59/100
- 0Tools and files. 3 referenced file(s) missing: scripts/research_probe.py, scripts/paper_downloader.py, scripts/agent_task_generator.py
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 96 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2134 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 403: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 96 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.