hps-academic-paper
nexu-io/open-design · Agent Skill
Generates academic review presentations on given topics, structuring information for researchers and reviewers.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | nexu-io/open-design ↗ |
| Skill folder | hps-academic-paper |
| Stars | 94,749 |
| Bundled files | 1 |
| License | Apache-2.0 |
| Last updated | July 13, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “hps-academic-paper” skill from mozgi.io (https://mozgi.io/skills/hps-academic-paper/) for me. 1. Download the archive: https://mozgi.io/skills/hps-academic-paper/download If it fails, take the skill folder from the source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/examples/hps-academic-paper 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “hps-academic-paper” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/hps-academic-paper/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/nexu-io/open-design.git /tmp/open-design mkdir -p .claude/skills cp -r /tmp/open-design/plugins/_official/examples/hps-academic-paper .claude/skills/hps-academic-paper
Restart Claude Code — the skill appears in the list; call it manually with /hps-academic-paper. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/nexu-io/open-design.git /tmp/open-design mkdir -p .agents/skills cp -r /tmp/open-design/plugins/_official/examples/hps-academic-paper .agents/skills/hps-academic-paper
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $hps-academic-paper. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/nexu-io/open-design.git /tmp/open-design mkdir -p .cursor/skills cp -r /tmp/open-design/plugins/_official/examples/hps-academic-paper .cursor/skills/hps-academic-paper
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/nexu-io/open-design.git /tmp/open-design mkdir -p .gemini/skills cp -r /tmp/open-design/plugins/_official/examples/hps-academic-paper .gemini/skills/hps-academic-paper
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyAcademic Paper(学术论文风)
A locked, single-theme deck plugin in the html-ppt-studio family, ported from
the MIT-licensed lewislulu/html-ppt-skill ↗
academic-paper theme (assets/themes/academic-paper.css on the upstream
templates/deck.html scaffold). The register is a LaTeX article walking on
stage: paper-white ground, ink-black serif text, link-blue underlined
citations, italic kickers, hairline rules everywhere, zero rounded corners,
no shadows. It reads like Computer Modern even when Computer Modern is not
installed.
**Start from example.html in this plugin folder. It is the proven seed: keep
its :root token sheet, base/slide-system CSS, academic device classes, deck
chrome and the entire navigation script verbatim, then replace only the slide
content. Do not rewrite the design system, and do not introduce any color or
font outside this spec.**
Design tokens (locked — reproduce verbatim in :root)
:root{
--bg:#fdfcf8; --bg-soft:#f7f5ed; --surface:#ffffff; --surface-2:#f5f3ea;
--border:rgba(20,20,20,.14); --border-strong:rgba(20,20,20,.35);
--text-1:#0a0a0a; --text-2:#333333; --text-3:#707070;
--accent:#1a3a7a; /* link blue — citations, "ours" data, best numbers */
--accent-2:#0a0a0a; /* ink — rules, heavy structure */
--accent-3:#8a1a1a; /* sparing dark red — errata/negative only */
--good:#1a5a2a; --warn:#8a6a1a; --bad:#8a1a1a;
--grad:linear-gradient(135deg,#1a3a7a,#0a0a0a);
--grad-soft:linear-gradient(135deg,#e8edf8,#f5f3ea);
--radius:0px; --radius-sm:0px; --radius-lg:0px;
--shadow:none;
--shadow-lg:0 1px 2px rgba(0,0,0,.1);
--font-sans:'Latin Modern Roman','Playfair Display','Noto Serif SC',Georgia,serif;
--font-serif:'Latin Modern Roman','Playfair Display','Noto Serif SC',Georgia,serif;
--font-mono:'JetBrains Mono',SFMono-Regular,Menlo,monospace;
--font-display:'Latin Modern Roman','Playfair Display','Noto Serif SC',Georgia,serif;
--letter-tight:-.01em; --letter-normal:0;
--ease:cubic-bezier(.4,0,.2,1);
}
Hard color discipline: paper white, ink black, link blue, and the three
semantic statuses are the entire palette. --accent-3 dark red appears
only for errata, negative deltas or "withdrawn/deprecated" marks. Never add
gradients beyond the two declared tokens, never round a corner, never cast a
shadow stronger than --shadow-lg.
Typography
- All three display slots are serif.
Latin Modern Romanis named first
so machines with LaTeX fonts get the real thing; Playfair Display (+
Noto Serif SC for CJK, then Georgia) is the webfont fallback. Google
Fonts @import for Playfair Display (incl. italics), Noto Serif SC and
JetBrains Mono are the only permitted external references.
- Headings weight 700, body 400, line-height 1.6. No uppercase headings, no
negative tracking beyond --letter-tight:-.01em.
.kickeris the theme signature: *italic*, link blue, sentence case,
letter-spacing:0, weight 400 — never uppercase, never bold.
- Numbers in stats/tables use
font-variant-numeric:tabular-nums.
Academic devices (theme-signature components — use them)
| class | device |
|---|---|
| .rule / .rule-double | hairline rule / LaTeX titlepage double rule (2px over 1px) |
| .abstract | italic abstract environment between two hairline rules, bold lead word |
| .cite | [n] citation anchor — mono, link blue, underlined |
| .figure + .figcaption | ruled figure box with numbered italic caption (<b>Figure 1:</b> …) |
| .booktabs | three-line table: 2px top/bottom rules, 1px header rule, no vertical rules; .best bolds winners in link blue |
| .footnote | dagger small print under a hairline rule |
| .references | hanging [n] bibliography list, titles in <i> |
| .toc-list | numbered outline with hairline separators and italic timing column |
| .section-num | oversized ghost numeral (in --surface-2) for section dividers |
Every figure and table must carry a numbered caption — that is what makes
the deck feel like a paper. Diagrams are ink-line inline SVG (1.5px ink
strokes, serif labels, the "ours" box tinted #e8edf8/link blue); charts are
pure CSS bars on a heavy ink axis with baselines in muted --surface-2 and
exactly one link-blue "ours" bar. No chart libraries, no remote images.
Layout masters (all demonstrated in example.html, 11 pages)
1. cover — italic venue kicker, double rule, serif title, author line with
superscript affiliations, hairline rule, affiliation small print
2. toc/outline — .toc-list numbered contents
3. section-divider — ghost numeral + ink rule
4. abstract + contributions — .abstract beside a .check list
5. stat-highlight — one giant tabular number in link blue + .footnote CI
6. method figure — inline SVG pipeline in .figure with Figure caption
7. chart-bar — CSS bar chart, muted baselines vs blue "ours", Figure caption
8. booktabs table — Table caption, .best winners
9. big-quote — italic serif epigraph with precise attribution
10. conclusions — two ruled cards (shown / open problems) + artifact link
11. thanks/references — .references bibliography + contact line
Compose decks from these masters; sequence
cover → outline → (divider → 2–4 content pages) × N → conclusions → references.
Slide system & runtime (keep verbatim)
- One self-contained HTML file; inline
<style>+<script>; zero build,
zero external JS. Each page is <section class="slide" data-title="…">
inside <div class="deck" id="deck"> — a horizontal scroll-snap strip,
one 100vw × 100vh screen per slide (16:9 / 1280×720 baseline, fluid via
clamp()), padding 72px 96px, no internal scrolling.
- Fixed chrome:
.deck-header(running head: short title · venue, italic),
.deck-footer (attribution + N / total counter), 2px .progress-bar in
link blue.
- Keyboard:
←/→/Space/PageUp/PageDown/Home/End;#/Nhash deep links via
history.replaceState in try/catch (srcdoc-safe). The script's dual
capture-phase listeners with Event-identity dedupe, .deck scroll sync and
body auto-focus fix real iframe-host bugs — do not simplify them away.
This variant is theme-locked: there is no T theme cycling.
- Speaker notes: one hidden
<div class="notes">…</div>per slide. - Animations are restrained: at most one
anim-rise-in/anim-fade-uphero
plus one anim-stagger-list per slide. No 3D, no glitch, no confetti —
this is a lecture hall, not a launch party.
Authoring checklist
1. Copy example.html; keep all <style> blocks and the <script> verbatim.
2. Replace the 11 demo slides with your content using the masters above.
3. Real content, real numbers, real (or plausibly fictional) citations — no
lorem ipsum; number every Figure/Table caption consecutively.
4. Keep the running head and footer attribution updated; the script computes
the N / total counter automatically.
5. Write 1–3 sentence speaker notes per slide in .notes.
6. Verify: arrows + Space navigate, #/5 deep-links, no slide overflows
vertically, no color or font outside the token sheet.
Attribution
Theme tokens and the deck scaffold come from the upstream MIT-licensed
(© lewis <[email protected]>) — theme academic-paper. The LICENSE
file ships alongside this skill; keep it in place when redistributing.
Frequently asked questions
What does the hps-academic-paper skill do?
Generates academic review presentations on given topics, structuring information for researchers and reviewers.
How do I install hps-academic-paper?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with hps-academic-paper?
Skills are plain Markdown instructions (the Agent Skills format), so hps-academic-paper works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is hps-academic-paper free?
The skill is published openly by nexu-io under the Apache-2.0 license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.