cover-letter
Skill4 starsChanged 42 days agoMITView on GitHub
Prepare a journal submission cover letter when requested or during Stage 6.
36 other projects use a version of this.
Adopted by
Most recently taken up by
- carriegale2710/resume-tailortheir own version, first seen Nov 16, 2026
- Axect/skillstheir own version, first seen Nov 16, 2026
- Bellistri-Nick/pm-skillstheir own version, first seen Nov 15, 2026
- Muvon/octomind-taptheir own version, first seen Nov 12, 2026
- thesun4sky/jobstacktheir own version, first seen Nov 10, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use interview-prep, tailor-resume and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillinterview-prep
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
Also in 8 projects that use this
proficientlyjobsSkilltailor-resume
Tailor your resume for a specific job posting
Also in 4 projects that use this
rhowardstoneSkilljob-search
Search for jobs across multiple boards and company career pages. Use when looking for new positions to apply to.
Also in 4 projects that use this
aslavchevSkillmock-interview
Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.
Also in 3 projects that use this
rhowardstoneSkillapply
Research-backed job application workflow emphasizing relationship-building over mass applications
Also in 3 projects that use this
JDerekLomasSkillliterature-review
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
Also in 3 projects that use this
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- claude-office-skills/skills★ 433same name
- proficientlyjobs/proficiently-claude-skills★ 389same name
- thesun4sky/jobstack★ 216same name
- matthewdigiuseppe/MStack★ 17same name
- Mahashwetha/Job-search-email-system-claude★ 12same name
- pradyumnasagar/open-research-skills★ 8same name
- Muvon/octomind-tap★ 6same name
- xcrrr/claude-skills★ 6same name
- Axect/skills★ 4same name
26 more not listed
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- academic-humanizerSkill
- citation-verificationSkill
- claim-numerics-auditSkill
- experiment-planSkill
- experiment-runnerSkill
- journal-scoutSkill
- paper-auditSkill
- paper-illustrationSkill
- paper-planSkill
- paper-writeSkill
- research-data-auditSkill
- research-ideationSkill
- research-publicationSkill
- research-quality-gateSkill
- research-refineSkill
- result-to-claimSkill
- scientific-figure-makingSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use the target journal's current requirements when they exist.
- Distinctive: line 47
Done when: every stated contribution matches the manuscript, has the appropriate evidence, and no extra contribution was invented for the …
- Distinctive: line 50
Don't say "this fits the scope of your journal." Show it:
- Distinctive: line 51
When verified and genuinely relevant, reference specific recent work from this journal.
- Distinctive: line 60
No competing interests (or declare them)
- Distinctive: line 67
Follow the journal's stated length and format.
- Distinctive: line 69
Every claim in the CL must match the manuscript: No exaggeration in the CL that the paper can't back up.
- Distinctive: line 71
Make journal fit specific and evidence-based: Avoid generic praise or unsupported assumptions about editorial preference.
- Distinctive: line 72
Match contribution count to the paper: If the paper has 3 contributions, the CL has 3.
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cover Letter
Generate a submission cover letter tailored to the target journal and manuscript contributions.
Input
paper/main.tex— the manuscript (for key contributions and results)docs/02_journal_scouting.md— target journal scope, recent papers, editor expectationsdocs/03_idea_report.md— core contributions and novelty
Typical structure
Use the target journal's current requirements when they exist. The following sequence is a compact default, not a mandatory paragraph count.
P1: Submission Statement
One sentence: what you are submitting, the title, and to which journal.
Done when: Submission statement written in one sentence specifying title, manuscript type, and target journal.
P2: Problem + Context
What real problem does this work solve? Why does it matter now? Use concrete, verified context; include scale or numbers only when the source supports them. Keep it tight — this is a cover letter, not the introduction.
Done when: The problem and relevance are stated concisely using supported facts; no number is invented to fill a template.
P3: Scientific Question + Gap
What fundamental obstacle makes this problem unsolved? State the research question. If possible, abstract it beyond the specific domain to show why the answer matters to readers outside your subfield.
Done when: Research question stated with gap identified; significance articulated beyond the specific domain.
P4: Contributions (with Evidence)
Present only the manuscript's verified contribution set. Number contributions when that improves readability. Each one:
- Has a name, not "Module A"
- States the mechanism or finding, not just the module name
- Includes a number when available
- Is verifiable from the manuscript
Pattern:
- [Finding/Insight name]. [One sentence describing what was discovered and how]. [Evidence: N samples, metric = value].
- [Method/System name]. [One sentence on what it does and why it's transferable].
- [Capability/Impact name]. [One sentence on what this enables that couldn't be done before].
Done when: every stated contribution matches the manuscript, has the appropriate evidence, and no extra contribution was invented for the letter.
P5: Fit with Journal (Specific, Not Generic)
Don't say "this fits the scope of your journal." Show it:
- When verified and genuinely relevant, reference specific recent work from this journal; do not add token citations merely to flatter the venue.
- Name the sub-area or theme within the journal's scope that this work extends
- Close the loop: how does this work advance the conversation already happening in this journal?
Done when: the journal-fit paragraph names the relevant scope or conversation and uses only verified, genuinely relevant examples when needed.
P6: Declarations
- Original, not published elsewhere, not under consideration
- All authors approved
- No competing interests (or declare them)
- Any AI usage disclosure if required
Done when: Each required declaration has a recorded author/policy source. Never infer originality, non-simultaneous submission, author approval or absence of competing interests. Mark unconfirmed items in a review draft and block the final letter until resolved; reuse existing confirmations when still applicable.
Rules
- Follow the journal's stated length and format; absent a rule, keep the letter concise and normally near one page.
- Address the appropriate editor by name only when the current role and spelling have been verified; otherwise use a neutral editorial salutation.
- Every claim in the CL must match the manuscript. No exaggeration in the CL that the paper can't back up.
- Don't summarize the paper. State the contribution and its significance. The editor will read the abstract for summary.
- Make journal fit specific and evidence-based. Avoid generic praise or unsupported assumptions about editorial preference.
- Match contribution count to the paper. If the paper has 3 contributions, the CL has 3. Don't invent extra ones for the CL.
References
| File | Open when |
references/cover-letter-patterns.md | Writing the cover letter. 5-paragraph structure, common mistakes, length guidelines. |
Output
Use the target journal's confirmed format and the project's existing toolchain. For a LaTeX deliverable, paper/cover_letter.tex with the standard letter class is a suitable default; compile with the existing compatible engine and inspect the output. If the journal requires plain text or another document format, prepare that format directly. Do not introduce a LaTeX or engine dependency solely to produce a cover letter.
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.

