submission-package
Skill2 starsChanged 35 days agoMITView on GitHub
Assembles the cover letter, title page, funding and conflict declarations, CRediT contributions, AI-use statement, suggested reviewers, and upload checklist for a locked journal. Use when the user says "cover letter", "submission package", "competing interests", "data availability", "CRediT", "suggested reviewers", "highlights", "visual abstract", "field guide", or "ready to submit". Do not use to click Submit, sign a copyright transfer, pay an APC, or invent reviewer email addresses.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kfangw/research-opstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kfangw/research-ops★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/literature-review.mdcCursor rule
- exemplar-review-analysisSkill
- figure-permissionsSkill
- journal-selectionSkill
- literature-screeningSkill
- manuscript-polishingSkill
- paper-deep-readingSkill
- reviewer-responseSkill
- review-figures-and-tablesSkill
- review-orchestratorSkill
- review-outline-builderSkill
- review-project-setupSkill
- review-scoping-and-gapsSkill
- review-section-drafterSkill
- review-writingSkill
- search-export-and-dedupSkill
- search-strategy-builderSkill
- zotero-library-syncSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Read the locked journal's author page again if the shortlist date is not today.
- Very specific: line 47
No funding uses the sentence No specific funding was received for this review.
- Very specific: line 49
No conflicts uses The authors declare no competing interests.
- Distinctive: line 67
If pandoc is missing, use:
- Very specific: line 76
Run a draft check while placeholders remain, then the ready check.
- Distinctive: line 94
After the user says the package is the one they will submit, append:
- Very specific: line 98
Use the gate name in shared/gates.md when that file exists (fallback final_submit).
- Distinctive: line 123
Every author has at least one real CRediT role, and every role is one of the 14.
- Distinctive: line 130
Do not invent funding, conflicts, ORCIDs, reviewer names, or emails.
- Distinctive: line 131
Do not list an AI system as an author or cite an AI system as the source of a scientific claim.
- Distinctive: line 132
Do not promise the editor that the work is novel, first, or suitable for a fast track.
- Distinctive: line 133
Do not create a journal account or agree to a license.
- Very specific: line 137
Stop. The user submits. When a decision letter arrives, use reviewer-response.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Submission package
Opening
On first use in a project, say this verbatim:
I am the submission package. I assemble the files for you to upload, and I do not submit the manuscript.
When to use
The journal is locked, 10-polish/manuscript_polished.docx exists, citation and overclaim checks passed, and validate_ledger.py --strict passed. You prepare files. The user uploads them.
Inputs (paths) / Preconditions
<project>/11-journal/journal_shortlist.md— locked journal, double-anonymized line, reference style, word limit.<project>/10-polish/manuscript_polished.docxandmanuscript.md<project>/08-figures/figure_ledger.csvand<project>/12-permissions/permissions_log.csvif any item was reused or adapted<project>/evidence/evidence_table.csvfor the data-availability statement- Author names, affiliations, emails, funding, and conflicts, supplied by the user. If a fact is missing, leave the official placeholder and do not guess.
- Templates in
references/ - ICMJE recommendations: https://www.icmje.org/recommendations/
- AI use by authors: https://www.icmje.org/recommendations/browse/artificial-intelligence/ai-use-by-authors.html
- COPE on AI authorship: https://publicationethics.org/guidance/cope-position/authorship-and-ai-tools
- CRediT roles: https://credit.niso.org/contributor-roles-defined/
<suite> and <project> are the suite directory and the review folder.
Procedure (numbered steps)
- Read the locked journal's author page again if the shortlist date is not today. Submission rules change. If the page disagrees with the shortlist, stop and update the shortlist before writing the letter.
- Copy the five templates in
references/into<project>/13-submission/under the same filenames:cover_letter.md,title_page.md,declarations.md,suggested_reviewers.md,file_checklist.md. - Cover letter, from
references/cover_letter.md. One page, at most 500 words. It must say the manuscript is not under consideration elsewhere (ICMJE overlapping publication). Name the article type the journal actually uses. Do not claim the review is the first, do not mention an impact factor, and do not ask for a decision date. - Title page, from
references/title_page.md. Author order and corresponding author come from the user. If the journal isDouble-anonymized: yes, this file is separate and the manuscript file has no author names. Add that checklist line:Manuscript contains no author names. ORCID, if the user supplies one, is checked against https://orcid.org/ and must pass the checksum. Do not invent an ORCID. - Declarations, from
references/declarations.md. Keep one funding paragraph and one AI paragraph.- No funding uses the sentence
No specific funding was received for this review. - A grant needs the funder name and a number that the user provided.
- No conflicts uses
The authors declare no competing interests.Otherwise describe the interest in the author's words. - Data availability names the evidence table. Do not invent a repository DOI.
- If no AI tool was used to draft, edit, or make figures, keep the no-AI sentence in the template. If one was used, replace that sentence with the disclosure block in the template comments: tool name, version, what it did, that humans take full responsibility, and that the tool is not an author (ICMJE and COPE, links above). Also put that disclosure in the cover letter and in the manuscript acknowledgements or methods, matching the journal.
- CRediT roles are only the 14 names on https://credit.niso.org/contributor-roles-defined/. Optional degree is
lead,equal, orsupporting. Contribution lines use the same names, in the same order, as the title page. CRediT does not replace the four ICMJE authorship criteria: substantial contribution, drafting or critical revision, final approval, and accountability. AI tools are not authors.
- No funding uses the sentence
- Suggested reviewers, from
references/suggested_reviewers.md. Default is 3 to 5 people. If the journal page states a number, setRequired count:to that number and setRule source:toverified on YYYY-MM-DD at https://.... If the page is silent,Rule source: project defaultand use the checks in the template: not a coauthor in the evidence table, not at an author institution, not a supervisor or student, no family link, has not seen this manuscript. Anyone you cannot check stays out of the suggested list. Put them under## Do not suggestwithConflict check: unverified. Email addresses come from an official staff page the user opened. Do not guess, and do not use anexample.comaddress. - Checklist and upload order, from
references/file_checklist.md. Follow the journal's upload order when the author page lists one. Tick a box only when that file exists. SetHighlights:andVisual abstract:torequiredornot requiredfrom sentences you read on the author page. When a line isnot required, do not draft that item. When it isrequired, draft it from claims already in10-polish/manuscript.md:highlights.md: use the bullet count on the author page when it states one, and otherwise three to five. Each bullet repeats a clause already in the polished manuscript and keeps that sentence's evidence ID. When the page states a character limit, addHighlights max characters: Nto the checklist and keep the reader-facing clause within N characters. The highlights guide at https://www.elsevier.com/researcher/author/tools-and-resources/highlights uses three to five bullets of at most 85 characters including spaces; apply 85 only when the page you opened states that limit.visual_abstract.md:- Message:copied from the polished manuscript,- Evidence IDs:that already appear there, and- Rights: original. A visual or graphical abstract is one original image, not this markdown file and not a crop or reuse of a published figure (https://www.elsevier.com/researcher/author/tools-and-resources/graphical-abstract). Before the ready check, also write13-submission/visual_abstract.svg(valid XML, wording in<text>elements, no embedded image) and13-submission/visual_abstract.pdf.
- Write
portal_field_guide.md. The source line isSource: verified on YYYY-MM-DD at https://...for the author page you opened. Each field is a## Field:section with- Quoted line: "..."containing only a sentence you saw on that page. Do not paraphrase inside the quotes, and do not add a field you did not see. Do not include a login, a password, or a cookie. - Export the cover letter with the same word-processor path as the manuscript. Pandoc, when it is installed:
pandoc "<project>/13-submission/cover_letter.md" \
--from=markdown \
--to=docx \
--output="<project>/13-submission/cover_letter.docx"If pandoc is missing, use:
python3 <suite>/skills/submission-package/scripts/export_cover_letter.py \
--markdown <project>/13-submission/cover_letter.md \
--output <project>/13-submission/cover_letter.docxThe docx must contain the title and the sentence that the manuscript is not under consideration elsewhere. Still no login.
10. Run a draft check while placeholders remain, then the ready check. Pass --manuscript so required highlights and the visual abstract can be checked against the polished file:
python3 <suite>/skills/submission-package/scripts/check_package.py \
<project>/13-submission --draft \
--shortlist <project>/11-journal/journal_shortlist.md \
--manuscript <project>/10-polish/manuscript.md
python3 <suite>/skills/submission-package/scripts/check_package.py \
<project>/13-submission \
--shortlist <project>/11-journal/journal_shortlist.md \
--manuscript <project>/10-polish/manuscript.mdThe second command is the ready check. It fails on placeholders, unchecked boxes, example emails, a cover letter over 500 words, a missing cover-letter docx, a field guide without quoted author-page lines, and a title that does not match the title page.
- Show the user the letter and the reviewer list. Do not upload.
- After the user says the package is the one they will submit, append:
YYYY-MM-DD | submission-package | final submit handed to the user | human
Use the gate name in shared/gates.md when that file exists (fallback final_submit). You still do not log in.
Human gate(s)
Final submit. The user logs in, uploads, pays any APC, and signs any copyright form. You stop when the ready check prints OK submission package and the user has the file list. You do not click Submit. An optional decision card may come first (shared/decision_cards.md): four labeled options, one preferred, and a custom option rewritten as a plan with its risks. Only the exact sentence I confirm the package is ready for me to submit sets the lock. A needs-permission row in 08-figures/panel_crop_ledger.csv blocks this lock.
Outputs (exact paths + formats)
<project>/13-submission/cover_letter.md<project>/13-submission/cover_letter.docx<project>/13-submission/title_page.md<project>/13-submission/declarations.md<project>/13-submission/suggested_reviewers.md<project>/13-submission/file_checklist.md<project>/13-submission/portal_field_guide.md<project>/13-submission/highlights.mdonly when the author page requires highlights<project>/13-submission/visual_abstract.md,visual_abstract.svg, andvisual_abstract.pdfonly when the author page requires a visual or graphical abstract
Quality checklist
- The ready command prints
OK submission package. - Cover-letter title and corresponding-author email match the title page, and the docx contains that title.
- The field guide quotes only lines from the author page opened that day.
- Required highlights repeat claims already in the polished manuscript and fit the count and character limit recorded from the author page.
- A required visual abstract repeats a polished-manuscript claim, and its SVG is editable text with a PDF beside it.
- Every author has at least one real CRediT role, and every role is one of the 14.
- Suggested reviewers are
Conflict check: clear, with institutional emails the user verified. - Permissions receipts exist for every non-original figure, or those figures were replaced.
- The manuscript file for a double-anonymized journal contains no author names.
Guardrails
- Do not invent funding, conflicts, ORCIDs, reviewer names, or emails.
- Do not list an AI system as an author or cite an AI system as the source of a scientific claim.
- Do not promise the editor that the work is novel, first, or suitable for a fast track.
- Do not create a journal account or agree to a license.
Next step
Stop. The user submits. When a decision letter arrives, use reviewer-response.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

