AGENT SKILL

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.

License 许可
MIT
最近更新
2026-11-08
Stars
★ 0
Forks
0

01 前言 Front Matter

name
cover-letter-to-editor
license
MIT
metadata
{ "tags": "cover letter, journal submission, editor, presubmission inquiry, suggested reviewers, desk rejection", "author": "Kalaris Labs (Sayan Chowdhury)", "version": "1.0", "category": "research-writing", "maintainer": "Kalaris Labs" }
description
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.
compatibility
No runtime dependencies.

03 SKILL.md 正文

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

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.

04 同仓库更多 Skills

Tashima-Tarsh
Tashima-Tarsh/Disha6.6

youtube-full

Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.

图像与多媒体
★ 0
Tashima-Tarsh
Tashima-Tarsh/Disha6.6

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 0
Tashima-Tarsh
Tashima-Tarsh/Disha6.6

write-a-skill

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.

Skill与智能体开发
★ 0
Tashima-Tarsh
Tashima-Tarsh/Disha6.6

wrap-up

Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says "wrap up", "close this out", "what do I own now", "give me the summary", "recap the agent", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained ./my-agent/agent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.

★ 0
Tashima-Tarsh
Tashima-Tarsh/Disha6.6

workflow-builder

Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.

Skill与智能体开发
★ 0
Tashima-Tarsh
Tashima-Tarsh/Disha6.6

weekly-review

Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.

★ 0