Individual skill

paperFig

Design, implement, revise, and validate publication-quality scientific figures from references, existing plotting code, and real project data. Trace every figure to source code and inputs; deconstruct reference figures; plan the scientific story and multi-panel structure; build complex model architecture and statistical panels; enforce a consistent visual system; and render-verify PDF/SVG/PNG outputs. Use for 科研配图, 论文配图, 找图的源代码, 参考图复刻与改造, 模型框架图, 多面板主图, figure redesign, or standardizing a research-figure process.

paperspine5/core/02_PaperFigure/02_paperFig_skill/SKILL.md

Read pinned source

Source commit 42312b8d9c76ab25990cddfd76e3622276854118

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
6,262
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# paperFig

Create scientifically faithful, publication-quality figures through a
repeatable process from evidence inventory to final render QA.

This skill governs the **research-figure process only**. It does not include
anonymization, data perturbation, synthetic replacement, identifier removal,
or privacy guarantees. If the user separately requests those operations,
treat them as an additional workflow with an explicit data-release contract;
do not silently mix them into ordinary scientific plotting.

## Mandatory routing

Read the following references before acting:
Back to top