/paper-figures
Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the
Claude Code
$ npx -y skills add Muuuun/luxas --skill paper-figures --agent claude-code
Codex
$ npx skills add Muuuun/luxas --skill paper-figures -a codex -y
Cursor
$ npx skills add Muuuun/luxas --skill paper-figures -a cursor -y
Gemini CLI
$ npx skills add Muuuun/luxas --skill paper-figures -a gemini-cli -y
GitHub Copilot
$ npx skills add Muuuun/luxas --skill paper-figures -a github-copilot -y
OpenCode
$ npx skills add Muuuun/luxas --skill paper-figures -a opencode -y
Windsurf
$ npx skills add Muuuun/luxas --skill paper-figures -a windsurf -y
SKILL.md
paper-figures.SKILL.mdname: paper-figures
description: Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the extract-figures script as {{EXTRACT_FIGURES}} — use that value wherever this skill writes `extract-figures`.Paper Figures Skill
Figures are information. A survey/review report covering downloaded papers MUST include key figures — architecture diagrams, experimental results, comparisons. Do NOT write a text-only survey when figures are available.
3-step workflow
Step 1 — Extract figures from downloaded papers
Your brain prompt supplies the script's absolute path as `{{EXTRACT_FIGURES}}`. Invoke it once per paper:
{{EXTRACT_FIGURES}} data/papers/<paper-id>.pdf # single PDF
{{EXTRACT_FIGURES}} data/papers/<arxiv-id> # arXiv source directoryThis creates `data/papers/<id>_figures/` with extracted images and a `manifest.json` listing each figure with caption and page number.
Step 2 — Review captions and classify every figure
Read every manifest:
cat data/papers/*_figures/manifest.json
Record your decisions in `notes/memory.md` under a `## Figure Review` section. Every figure must end up in one of three states:
- **USE** — essential for understanding the topic; will be included in the report
- **SKIP** — irrelevant, redundant, or low quality
- **UNREVIEWED** — caption not yet read (only acceptable as a transient state)
Select figures that are:
- Essential for understanding the topic (architecture diagrams, system schematics)
- Key experimental results that support your narrative
- Useful comparisons across methods, systems, or time periods
- Visually informative (not just tables rendered as images)
Step 3 — Include `USE` figures in the report
For each figure marked `USE`, embed it directly in LaTeX:
\begin{figure}[t]
\centering
\includegraphics[width=\linewidth]{../data/papers/<id>_figures/<filename>}
\caption{<Your caption describing the figure in the context of your survey>. Adapted from \cite{<key>}.}
\label{fig:<label>}
\end{figure}Rules
- **Coverage**: survey/review reports include at least 3-5 `USE` figures from downloaded papers, in addition to any figures you generate yourself.
- **Captions**: write your OWN caption in the context of the survey narrative — do not copy the original caption.
- **Attribution**: always cite the source paper with `\cite{}`.
- **No skipping the review step**: every extracted figure must be classified before writing the report.
- **Complementary**: you may also generate your own figures (see `skills/matplotlib-figures/SKILL.md`) for data summaries, timelines, or cross-paper comparisons not found in existing figures.
Read more
name: paper-figures
description: Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the extract-figures script as {{EXTRACT_FIGURES}} — use that value wherever this skill writes `extract-figures`.Paper Figures Skill
Figures are information. A survey/review report covering downloaded papers MUST include key figures — architecture diagrams, experimental results, comparisons. Do NOT write a text-only survey when figures are available.
3-step workflow
Step 1 — Extract figures from downloaded papers
Your brain prompt supplies the script's absolute path as `{{EXTRACT_FIGURES}}`. Invoke it once per paper:
{{EXTRACT_FIGURES}} data/papers/<paper-id>.pdf # single PDF
{{EXTRACT_FIGURES}} data/papers/<arxiv-id> # arXiv source directoryThis creates `data/papers/<id>_figures/` with extracted images and a `manifest.json` listing each figure with caption and page number.
Step 2 — Review captions and classify every figure
Read every manifest:
cat data/papers/*_figures/manifest.json
Record your decisions in `notes/memory.md` under a `## Figure Review` section. Every figure must end up in one of three states:
- **USE** — essential for understanding the topic; will be included in the report
- **SKIP** — irrelevant, redundant, or low quality
- **UNREVIEWED** — caption not yet read (only acceptable as a transient state)
Select figures that are:
- Essential for understanding the topic (architecture diagrams, system schematics)
- Key experimental results that support your narrative
- Useful comparisons across methods, systems, or time periods
- Visually informative (not just tables rendered as images)
Step 3 — Include `USE` figures in the report
For each figure marked `USE`, embed it directly in LaTeX:
\begin{figure}[t]
\centering
\includegraphics[width=\linewidth]{../data/papers/<id>_figures/<filename>}
\caption{<Your caption describing the figure in the context of your survey>. Adapted from \cite{<key>}.}
\label{fig:<label>}
\end{figure}Rules
- **Coverage**: survey/review reports include at least 3-5 `USE` figures from downloaded papers, in addition to any figures you generate yourself.
- **Captions**: write your OWN caption in the context of the survey narrative — do not copy the original caption.
- **Attribution**: always cite the source paper with `\cite{}`.
- **No skipping the review step**: every extracted figure must be classified before writing the report.
- **Complementary**: you may also generate your own figures (see `skills/matplotlib-figures/SKILL.md`) for data summaries, timelines, or cross-paper comparisons not found in existing figures.
An autonomous research agent: from a one-line question to a compiled, reviewed LaTeX report. luxas.im · Gallery · Quick start · How it works · Architecture notes · Contributing Give Luxas a research question in RESEARCH.md.
Other skills on luxas.
More skills from other plugins.
prompt-lookup
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…
ppt-master
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…
morph-ppt
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…
frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to…
Questions about paper-figures.
- Which coding agents can use paper-figures?
- paper-figures installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

