agentleFS
Xuzhen-LiXuzhen-Li/literature-review-skills/skills/submission-package/SKILL.md

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

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
  1. Distinctive:

    Read the locked journal's author page again if the shortlist date is not today.

    line 42
  2. Very specific:

    No funding uses the sentence No specific funding was received for this review.

    line 47
  3. Very specific:

    No conflicts uses The authors declare no competing interests.

    line 49
  4. Distinctive:

    If pandoc is missing, use:

    line 67
  5. Very specific:

    Run a draft check while placeholders remain, then the ready check.

    line 76
  6. Distinctive:

    After the user says the package is the one they will submit, append:

    line 94
  7. Very specific:

    Use the gate name in shared/gates.md when that file exists (fallback final_submit).

    line 98
  8. Distinctive:

    Every author has at least one real CRediT role, and every role is one of the 14.

    line 123
  9. Distinctive:

    Do not invent funding, conflicts, ORCIDs, reviewer names, or emails.

    line 130
  10. Distinctive:

    Do not list an AI system as an author or cite an AI system as the source of a scientific claim.

    line 131
  11. Distinctive:

    Do not promise the editor that the work is novel, first, or suitable for a fast track.

    line 132
  12. Distinctive:

    Do not create a journal account or agree to a license.

    line 133
  13. Very specific:

    Stop. The user submits. When a decision letter arrives, use reviewer-response.

    line 137

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

<suite> and <project> are the suite directory and the review folder.

Procedure (numbered steps)

  1. 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.
  2. 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.
  3. 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.
  4. Title page, from references/title_page.md. Author order and corresponding author come from the user. If the journal is Double-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.
  5. 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, or supporting. 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.
  6. Suggested reviewers, from references/suggested_reviewers.md. Default is 3 to 5 people. If the journal page states a number, set Required count: to that number and set Rule source: to verified on YYYY-MM-DD at https://.... If the page is silent, Rule source: project default and 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 suggest with Conflict check: unverified. Email addresses come from an official staff page the user opened. Do not guess, and do not use an example.com address.
  7. 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. Set Highlights: and Visual abstract: to required or not required from sentences you read on the author page. When a line is not required, do not draft that item. When it is required, draft it from claims already in 10-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, add Highlights max characters: N to 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 write 13-submission/visual_abstract.svg (valid XML, wording in <text> elements, no embedded image) and 13-submission/visual_abstract.pdf.
  8. Write portal_field_guide.md. The source line is Source: 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.
  9. 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.docx

The 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.md

The 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.

  1. Show the user the letter and the reviewer list. Do not upload.
  2. 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.md only when the author page requires highlights
  • <project>/13-submission/visual_abstract.md, visual_abstract.svg, and visual_abstract.pdf only 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.