BF clinical-data-extractor
Extract clinical trial data from pharmaceutical conference websites or PDF documents. Use when user provides a URL or PDF file containing innovative drug clinical trial data and needs structured extraction of: drug name, manufacturer, indication, clinical phase, trial name, conference, efficacy and safety data (presented as tables), and markdown output to "药品名称@适应症.md" file.
As a process F 53/100 · Will not run — References files that are not bundled: 图片URL, 药品名称_疗效曲线.png, 图片文件名.png
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: 3. 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: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Extract clinical trial data from pharmaceutical conference website… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: 图片URL - warning
missing-refreference to a missing file: 药品名称_疗效曲线.png - warning
missing-refreference to a missing file: 图片文件名.png - warning
missing-refreference to a missing file: URL - warning
missing-refreference to a missing file: 文件名.png
Process rating: all ten parameters 53/100
- 0Tools and files. 5 referenced file(s) missing: 图片URL, 药品名称_疗效曲线.png, 图片文件名.png
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 78 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2531 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 377: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.