pnasnexus-figures
Use to finalize PNAS Nexus display items — count figures and tables against the graphical-element budget, size to journal column widths, set legible fonts, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, and image integrity (raw, unprocessed images must be retained). Enforces figure rigor before submission.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-figures --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Display Items (pnasnexus-figures) ## When to trigger - Figures and tables push the page / graphical-element budget (`pnasnexus-writing`). - Fonts are unreadable at print size, or colors are not colorblind-safe. - Bar charts hide the underlying data (no points, no n). - Panels are screenshots of software output pasted into the figure. - You are unsure how figures count against the length limit. #
What does the pnasnexus-figures skill do?
Use to finalize PNAS Nexus display items — count figures and tables against the graphical-element budget, size to journal column widths, set legible fonts, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, and image integrity (raw, unprocessed images must be retained). Enforces figure rigor before submission.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-figures --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.