Cover Letter To Editor logo

Cover Letter To Editor

Organization
KalarisLabs
cover-letter-to-editor

Write journal submission cover letters, presubmission inquiries, transfer requests, and reviewer suggestion or exclusion lists that help a manuscript get past editorial triage. Use when submitting a paper to a journal, pitching a manuscript to an editor (presubmission enquiry), transferring after rejection, explaining a resubmission or appeal, or preparing the editor-facing parts of a submission such as the significance pitch, suggested reviewers and conflicts. Not for job or fellowship application letters.

Overview

PublisherKalarisLabs
Repositoryresearch-agent-skills
Skill namecover-letter-to-editor
Stars
91
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by KalarisLabs on GitHub. Read the source before you install it.

Installation

Install the Cover Letter To Editor AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/KalarisLabs/research-agent-skills/tree/main/skills/cover-letter-to-editor
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/KalarisLabs/research-agent-skills.git /tmp/research-agent-skills
mkdir -p .claude/skills
cp -r /tmp/research-agent-skills/skills/cover-letter-to-editor .claude/skills/cover-letter-to-editor
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cover Letter To Editor in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cover Letter To Editor on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cover Letter To Editor is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Cover Letters and Editor Communications

At selective journals an editor decides in minutes whether to send a paper to review. The cover letter is your only direct pitch: why this journal's readers need this result now. It does not summarize the abstract.

Before writing

Collect: the journal's scope/aims statement and article type; the main finding in one sentence with its key number; 1-3 recent papers in this journal your work builds on or challenges; required declarations (see the journal's guide).

Structure (one page)

  1. Opening: manuscript title, article type, journal. One sentence.
  2. The finding and why it matters, 2-4 sentences: the problem, what you found (with the key number), and what it changes. Written for a smart non-specialist editor.
  3. Why this journal: connect to the journal's readership and scope, and cite recent papers it published if you extend or overturn them. Avoid flattery.
  4. What is new vs. prior work: one or two sentences, concrete (larger cohort, first causal evidence, 10× faster, new mechanism).
  5. Declarations the journal asks for: not under consideration elsewhere, all authors approved, preprint server and DOI if posted, competing interests, related manuscripts under review, data availability.
  6. Reviewers: suggested reviewers (name, institution, email, expertise, no conflicts: not recent co-authors or same institution). Opposed reviewers with a brief, professional reason.
  7. Sign-off by the corresponding author with contact details.

Template

text
Dear Dr. [Editor surname],

We submit our manuscript "[Title]" for consideration as a [Article type] in [Journal].

[Problem in one sentence]. Here we show that [main finding with key number], using [approach
and scale]. This [resolves / overturns / enables] [specific consequence].

This work will interest [Journal]'s readers in [fields] because [reason]. It builds on
[Author et al., Journal, Year], which [what they showed], by [what you add].

The manuscript has not been published and is not under consideration elsewhere. All authors
approved the submission. A preprint is available at [server, DOI]. The authors declare [no
competing interests / the interests listed in the manuscript].

Suggested reviewers: [Name, Institution, email: expertise]. [...]
We request that [Name] not review this manuscript due to [brief professional reason].

Sincerely,
[Name, affiliation, email, ORCID]

Variants

  • Presubmission inquiry (Nature Portfolio, PLOS Biology, Cell Press and others): abstract + ~200-word pitch focused on significance. The editor answers "would consider" or "not suitable".
  • Transfer after rejection: mention the previous journal and decision. If reviews transfer, summarize how you addressed them.
  • Resubmission after reject-and-resubmit: list the main changes and link to the full response to reviewers (see rebuttal-and-response-to-reviewers).
  • Appeal: only for clear reviewer error or misunderstanding of central points. Be factual, brief and specific, and offer additional evidence.

Don'ts

  • Don't repeat the abstract, or use hype ("groundbreaking", "paradigm-shifting").
  • Don't overclaim beyond the manuscript or bury required declarations.
  • Don't suggest reviewers with conflicts, or friends, or fabricated contacts. This is research misconduct.
  • Don't exceed one page unless the journal asks for more.

Related skills

abstract-and-title, rebuttal-and-response-to-reviewers, reproducibility-statement, journal-format skills (nature-portfolio, science-aaas, cell-press, plos, ...), venue-templates.

Frequently asked questions

What does the Cover Letter To Editor AI skill do?

Write journal submission cover letters, presubmission inquiries, transfer requests, and reviewer suggestion or exclusion lists that help a manuscript get past editorial triage. Use when submitting a paper to a journal, pitching a manuscript to an editor (presubmission enquiry), transferring after rejection, explaining a resubmission or appeal, or preparing the editor-facing parts of a submission such as the significance pitch, suggested reviewers and conflicts. Not for job or fellowship application letters.

Why use Cover Letter To Editor on TypingMind?

Because you install it once and use it with any model. Cover Letter To Editor is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cover Letter To Editor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/KalarisLabs/research-agent-skills/tree/main/skills/cover-letter-to-editor. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cover Letter To Editor?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cover Letter To Editor?

As many as you like. As long as a model supports skills, you can use Cover Letter To Editor with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cover Letter To Editor AI skill free?

Yes. It is published on GitHub by KalarisLabs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇