BD research-paper-to-ppt-v2
将指定医学研究论文自动生成 PPTX 汇报文件的技能。用于用户给出单篇文献标题、PMID、DOI、InfoX-Med 文献 id 或可唯一定位该论文的信息时：先用 InfoX-Med 相关检索技能精确定位目标论文，再读取全文与原文图表，最后按基础研究型汇报大纲选择性生成 PPTX。适用于"根据这篇论文生成汇报PPT""把这篇 research paper 做成中文组会汇报""按文献生成带原图的PPT"等请求。强制要求：(1) PPT 必须优先使用论文原文图片；(2) 必须按大纲逻辑生成，但论文未涉及的章节直接跳过，不得插入空白页；(3) 若无法定位目标文献或无法获取全文，必须明确返回"检索失败，无法生成"，不得编造内容或伪造图片。默认输出文件名使用论文标题；默认版式为美观组会风格，包含目录页、结尾页和"谢谢！感谢批评指正！"结束文案；字体、图片、坐标等视觉规范必须严格遵循 visual-rendering-spec.md。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Exfiltration
net-redirectable-api-keyscripts/fetch_fullpaper.py:27Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
Files scanned: 21. 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")
Process rating: all ten parameters 49/100
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (research-paper-to-ppt-v2) differs from the folder (research-paper-to-ppt-v1)
- 100Tools and files. No external tools needed
- 100Steps. 201 steps
- 100Execution cost. Instruction body is 2016 tokens
- 100Running it twice. No mutating operations
- low 14 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)
- +3Output format is not stated: the model decides each time
- -32 of 9 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 417: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 201 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.