agentleFS
matthewdigiuseppematthewdigiuseppe/MStack/skills/cover-letter/SKILL.md

cover-letter

Skill17 starsChanged 3 months agoMITView on GitHub

Drafts the three-paragraph submission cover letter — fit to this journal, contribution, declarations — in 400 words or fewer. Use after a target journal is chosen, when the user asks for a cover letter or submission materials.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview-prep, tailor-resume and 6 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.
  • AnthropicSkill

    interview-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 7 projects that use this

  • proficientlyjobsSkill

    tailor-resume

    Tailor your resume for a specific job posting

    Also in 4 projects that use this

  • proficientlyjobsSkill

    job-search

    Search for jobs matching my resume and preferences

    Also in 4 projects that use this

  • aslavchevSkill

    mock-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

  • JDerekLomasSkill

    literature-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

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • +1 more from proficientlyjobs

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After /mstack:journal-fit.

    line 14
  2. Distinctive:

    Editor: Ask the user for the current editor's name and salutation if not in config.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 29 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.

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

/mstack:cover-letter

Stage: submit · Voice: the author addressing the editor

After /mstack:journal-fit. Read in 30 seconds; precision beats warmth.

Procedure

  1. Load .mstack/config.yaml (top-tier target journal), paper/sections/abstract.tex, the contribution sentence in .mstack/research-question.md.
  2. Editor. Ask the user for the current editor's name and salutation if not in config; editors change, so never guess from memory.
  3. Three paragraphs, ≤ 400 words:
    • Fit — what the paper does in one sentence and why it belongs in this journal, naming one or two recent papers there it is in conversation with; not "builds on the journal's strong tradition in X".
    • Contribution — the contribution sentence from /mstack:research-question, the headline finding, and the design that delivers it. No hedging.
    • Declarations — preregistration status + URL (from config); data and code availability; not under review elsewhere; conflicts of interest; IRB approval if applicable; word count; prior presentations or earlier versions.
  4. Sign-off: author name(s) and affiliation(s), one line.
  5. Save to submission/cover-letter.md (Markdown; convert to whatever the portal accepts at submission).
  6. Cross-check: editor correct and current; journal name spelled correctly throughout; within the journal's word limit; declarations cover everything the portal will ask.

Outputs

  • submission/cover-letter.md.
  • Summary block: word count, editor addressed, declarations covered; remind the user to set paper.status: "submitted" once the portal confirms.

Anti-patterns

  • Sycophancy. Editors do not need to hear their journal is excellent.
  • Generic fit. "Of interest to your readership" with no specific paper cited is noticeable.
  • Five paragraphs. Three.
  • Repeating the abstract. The letter situates the paper for this editor; the abstract cannot.

Next

Submit. On decision: /mstack:r-and-r for an R&R; /mstack:journal-fit again after a rejection.

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.