CC paper2assets
Extract a research paper PDF into a structured set of poster-agnostic assets reusable by any downstream renderer (paper2poster, paper2blog, paper2audio, paper2video). Produces a `<outdir>/` containing the paper's full text (assets/meta/text.txt), per-figure captions (assets/meta/captions.json), cleaned figure rasters (assets/figures/*.png + assets/meta/figures.json manifest), paper metadata (assets/meta/metadata.json: title / authors / institutes / venue / paper_url / code_url), institute logos (assets/logos/*), URL QR codes (assets/qr/*), and a 9-section structured paper summary (assets/meta/paper_spec.md). The bundle follows the Output Contract layout (deliverables at top, everything else under `assets/`). Use when the user wants to extract paper content into reusable assets, OR as the mandatory upstream stage of any paper-rendering pipeline — e.g., "extract this paper", "build paper assets", "get the figures and spec from this PDF", "paper2assets".
Extract a research paper PDF into a structured set of poster-agnostic assets reusable by any downstream renderer (paper2poster, paper2blog, paper2audio…
As a process C 56/100 · Has gaps — References files that are not bundled: assets/figures/..., assets/logos/..., assets/qr/...
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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(*)allowed-tools: Bash(*) Read Write Edit Grep Glob AskUserQuestion WebFetch WebSearch
Files scanned: 14. 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 a research paper PDF into a structured set of poster-agnos… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 15396 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: assets/figures/... - warning
missing-refreference to a missing file: assets/logos/... - warning
missing-refreference to a missing file: assets/qr/... - warning
missing-refreference to a missing file: assets/audio/... - warning
missing-refreference to a missing file: assets/meta/text.txt - warning
missing-refreference to a missing file: assets/meta/captions.json - warning
missing-refreference to a missing file: assets/meta/figures.json - warning
missing-refreference to a missing file: assets/figures/<page>_figure<n>.png - warning
missing-refreference to a missing file: assets/figures/_debug/<page>_figure<n>.png.bak - warning
missing-refreference to a missing file: assets/figures/_debug/<page>_figure<n>.marked-<NN>.png - warning
missing-refreference to a missing file: assets/meta/metadata.json - warning
missing-refreference to a missing file: assets/meta/paper_spec.md - warning
missing-refreference to a missing file: assets/logos/<slug>.{png,svg} - warning
missing-refreference to a missing file: assets/logos/logos.json - warning
missing-refreference to a missing file: assets/logos/ - warning
missing-refreference to a missing file: assets/qr/{paper,code}.png - warning
missing-refreference to a missing file: assets/meta/sections.json - warning
missing-refreference to a missing file: assets/meta/narration.json - warning
missing-refreference to a missing file: assets/figures/*.png - warning
missing-refreference to a missing file: assets/qr/ - warning
missing-refreference to a missing file: assets/logos/microsoft.png - warning
missing-refreference to a missing file: assets/logos/<slug>.png - warning
missing-refreference to a missing file: assets/logos/_venue.png - warning
missing-refreference to a missing file: scripts/generate_audio.py - note
edit-residuethe text marks something as outdated (lines 40, 75, 641): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 56/100
- 0Tools and files. 24 referenced file(s) missing: assets/figures/..., assets/logos/..., assets/qr/...
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 15396 tokens: crowds the task out of the window
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 78 steps, 3 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (42 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 965: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Structure: 19 headings
- +3Step-by-step instructions: 78 items
- +3Output format is stated explicitly
- +4Has examples (22 code blocks)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.