Submission Checklist Agent Skill
Stage-based submission checklists for papers/reports: pre-submission, submission, revision/rebuttal, camera-ready. Includes templates (cover letter, rebuttal matrix) and quality gates.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill submission-checklistWhat comes with it
4 546 bytes besides the instructionThe instruction itself
3 sections, as written by the authorSubmission Checklist（投稿 / 返修 / 相机就绪清单）
目标
把“投稿”拆成可执行、可复用的清单，避免典型的“低级错误导致 desk reject / major revision”的情况。
本 skill 不是写论文正文，而是为以下阶段提供可执行 checklist + 模板：
- Pre-submission（投稿前自检）
- Submission（提交包与系统填报）
- Revision / Rebuttal（返修与回复审稿意见）
- Camera-ready / Proof（相机就绪、校样阶段）
模板文件在 templates/：
pre-submission-checklist.mdrebuttal-response-matrix.mdcamera-ready-checklist.mdcover-letter.md
何时使用
触发关键词：
投稿、submission、cover letter、highlights返修、revision、rebuttal、回复审稿意见camera-ready、proof、校样checklist、自检清单
输入（最小信息）
1) 投向（期刊/会议/出版社）
2) 阶段（pre-submission / submission / revision / camera-ready）
3) 文档格式（LaTeX/Word/Quarto）
核心元规则（最容易漏）
1) Checklist 要“绑定产物”
每条 checklist 不是“建议”，而是能指向某个文件/位置：
- “图 2 导出 600dpi TIFF” →
figures/fig-02/out/fig-02.tiff - “统计检验写清楚” →
manuscript/methods.md#统计或main.tex对应段落
2) 返修回应要“可追踪”
每条 reviewer comment 必须对应：
1) 你做了什么改动（行动）
2) 你怎么回应（回复）
3) 改动在哪里（定位：页码/行号/章节）
模板：templates/rebuttal-response-matrix.md
交付建议（落地）
推荐固定输出一个 “submission bundle 目录”：
submission/cover-letter.mdsubmission/highlights.mdsubmission/submission-manifest.ymlrevision/rebuttal.md（返修时）
并在 submission-manifest.yml 记录每个关键检查项是否完成。
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take foryourhealth111-pixel/submission-checklist from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.