paper-suite

Files (24)

• marketplace.json · .claude-plugin/
• plugin.json · .claude-plugin/
• plugin.json · .codex-plugin/
• .gitignore
• CHANGELOG.md
• LICENSE
• README.md
• README.zh-CN.md
• SKILL.md
• VERSION
• list_md.py · _scripts/
• openai.yaml · agents/
• CROSS_PLATFORM.md · docs/
• install.py
• paper-suite.SKILL.md
• test_abstract_craft_contract.py · tests/
• test_installer.py · tests/
• test_monorepo.py · tests/
• test_monorepo_runner.py · tests/
• test_nature_visual_depth.py · tests/
• test_ppt_powerpoint_compat.py · tests/
• test_skill_packaging.py · tests/
• test_venue_adapt_visual.py · tests/
• test_writing_lint.py · tests/

SKILL.md (first lines)

# paper-suite Router

Route the user's request to the closest academic sub-skill. In the plugin / public install, the executable entry points are `$paper-writing`, `$paper-figure`, and `$paper-ppt`; invoke the matching sibling skill and continue its workflow. If working from the source checkout, read the local implementation folders `writing/`, `figure/`, and `ppt/` directly. Do not stop after announcing the route.

## Routes

| User intent | Use |
|---|---|
| polish / 润色 / improve prose / humanize academic text | `$paper-writing` -> `prose-polish` |
| write abstract / 改 abstract / abstract for a venue | `$paper-writing` -> `abstract-craft` |
| fit to NeurIPS / Nature / IEEE / TPAMI / venue style | `$paper-writing` -> `venue-fit` |
| learn style from 5-8 target papers | `$paper-writing` -> `venue-adapt` |
| style review / 审一下 / reads like AI | `$paper-writing` -> `style-k` or `deai-taste` |
| reviewer-eye pre-submission review | `$paper-writing` -> `reviewer-eyes` |
| reviewer comments / rebuttal / response letter | `$paper-writing` -> `rebuttal-helper` |
| line/bar/scatter/heatmap/violin/multi-panel plot | `$paper-figure` -> `plot-mpl` |
| architecture / pipeline / geometry diagram in LaTeX | `$paper-figure` -> `diagram-tikz` |
| roadmap / graphical abstract / draw.io layout | `$paper-figure` -> `diagram-drawio` |
| restyle an existing figure for a venue | `$paper-figure` -> `venue-switch` |
| check a figure for defects | `$paper-figure` -> `figure-anti-defect` |
| academic deck outline | `$paper-ppt` -> `deck-outline` |
| one academic slide | `$paper-ppt` -> `deck-page` |
| speaker notes | `$paper-ppt` -> `speaker-notes` |
| complete lab/conference/defense/funding deck | `$paper-ppt` -> `deck-deck` |

## Execution Rules

1. If one route clearly matches, state the route in one line, invoke the matching sibling skill (`$paper-writing`, `$paper-figure`, or `$paper-ppt`), and continue with its workflow.
2. If the request is ambiguous, ask one concise question before routing.
3. Prefer bundled references and scripts over improvising academic rules.
4. Do not invent results, citations, figures, datasets, or venue requirements.
5. When a sub-skill writes or modifies files, run its verification step before reporting completion.

## Packaged References

Use only references shipped inside this suite unless the user provides an external corpus or asks for current venue guidance. Key packaged references include:

- `$paper-writing` packaged references
- `$paper-figure` packaged references
- `$paper-ppt` packaged references

## Ambiguous Requests

- "改我的论文" -> ask whether they want prose polish, venue fit, AI-taste removal, reviewer-eye review, or rebuttal help.
- "做 PPT" -> ask which academic scenario: lab meeting, conference talk, thesis defense, or funding pitch.
- "我做了个图" -> ask whether they want to create, restyle, or inspect the figure.

From RTCartist/paper-suite, MIT.

More from RTCartist/paper-suite