paper2assets

A PDF-to-assets workflow for research papers. It extracts the paper's text, figure captions, and cleaned figures into a shared folder structure that other publishing tools can reuse.

In plain words
What is it for?
Use it to prepare a paper bundle containing full text, captions, figures, metadata, and supporting assets for later rendering workflows.
Why use it?
It avoids repeating PDF extraction when creating a poster, blog post, audio piece, video, or reel from the same paper.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/microsoft/researchstudio/paper2assets
Any agent
npx skills add microsoft/ResearchStudio --skill paper2assets
Clone the repo
git clone --depth 1 https://github.com/microsoft/ResearchStudio

Made for: Claude Code, Codex.

Per session 223 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 15,604 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00223 $0.15604
Opus 5 $0.00112 $0.07802
Sonnet 5 $0.00045 $0.03121
Haiku 4.5 $0.00022 $0.01560

Measured 3d ago against content hash c6baee00cc58, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

paper2assets scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

The scan reads SKILL.md. This mod also ships 12 executable files (scripts/build_package.py, scripts/crop_figure.py, scripts/extract_pdf.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ResearchStudio-Reel/skills/paper2assets/SKILL.md · 734 lines

How it starts

The opening of the file, as written. The whole thing — 734 lines — stays where its author put it; the contents beside it link to each section on GitHub.

paper2assets — paper PDF → reusable assets

One paper PDF in, a single <outdir>/ of poster-agnostic assets out, ready for any downstream renderer.

Output Contract (the shared layout every paper2* skill follows)

paper2assets defines the on-disk shape of every deliverable bundle in the pipeline. paper2poster, html2pptx, paper2blog, paper2video, and paper2reel all read from and write to a bundle laid out this way — a teammate adding or changing a downstream skill conforms to this contract.

Rules

  1. The bundle directory is named after the paper.
  2. The bundle's top level holds ONLY that skill's deliverable FILES — no loose intermediates, and as few folders as possible.
  3. Every dependency and intermediate (figures, logos, qr, audio, fonts, captions, slides, the spec / json / txt) lives under one assets/ container.

Layout

<paper-name>/
|-- <deliverable files>          # see the per-skill table below
|-- manifest.json                # package index (root-relative paths); the one allowed top-level non-deliverable
`-- assets/
    |-- figures/  logos/  qr/  audio/  fonts/   # runtime deps the deliverables reference
    `-- meta/                                    # build intermediates
        |-- paper_spec.md  sections.json  narration.json
        `-- captions.json  figures.json  metadata.json  text.txt

Deliverables reference assets with root-relative src paths -- assets/figures/..., assets/logos/..., assets/qr/..., assets/audio/... -- so the bundle is self-contained and movable (no absolute paths leak in). The path / file fields in figures.json, fetch_logos.py, and make_qr.py output already carry the assets/ prefix; downstream drops them into src verbatim.

Per-skill deliverables (top-level FILES):

Skill Top-level deliverable files
paper2assets manifest.json (+ the whole assets/ package)
paper2poster poster.html, poster.pdf, poster.png, poster.pptx
paper2blog blog_zh.docx, blog_en.docx
paper2video video.mp4, video_no_subtitles.mp4
paper2reel reel.html

Read the full file on GitHub · 734 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 734 lines · 0 tokens per session scan A c6baee00cc58

Subscribe to this mod's changes

paper2assets is a skill published in the GitHub repository microsoft/ResearchStudio (2,614 stars, last pushed 4d ago), licensed MIT. It adds 223 tokens to every session and 15,604 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.