scholarly-publishing
Use when planning an end-to-end scholarly publishing workflow, including manuscript source-of-truth, submission assets, revision/rebuttal files, camera-ready checks, reproducible build expectations, and publication package structure.
npx skills add foryourhealth111-pixel/Vibe-Skills --skill scholarly-publishing --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.
# Scholarly Publishing (论文投稿全流程) ## 你会得到什么（输出契约） 当用户说“我要投稿/返修/相机就绪/需要 LaTeX 工程化/写 rebuttal/写 cover letter”时，本 skill 负责把目标拆成**可交付的出版资产包**： - `manuscript/`：论文源文件（LaTeX / Word / Markdown 任一作为 *source-of-truth*） - `figures/`：每张图的源代码/源数据/最终导出要求（PDF/EPS/SVG/TIFF） - `supplement/`：补充材料（方法细节、附录、扩展实验、额外图表） - `submission/`：投稿所需文件（cover letter、graphical abstract、highlights、checklist、打包 zip） - `revision/`：返修资产
What does the scholarly-publishing skill do?
Use when planning an end-to-end scholarly publishing workflow, including manuscript source-of-truth, submission assets, revision/rebuttal files, camera-ready checks, reproducible build expectations, and publication package structure.
How do I install it?
Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill scholarly-publishing --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 foryourhealth111-pixel/Vibe-Skills, a repository with 2,593 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.