Generates a journal-ready cover letter from manuscript metadata, highlights, and journal-fit notes. Use when preparing an academic submission package and you need editor-facing language that clearly states novelty, relevance, declarations, and corresponding-author details.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Draft a submission-ready academic cover letter for a target journal. This skill is for editor-facing academic writing, not for inventing missing paper content.
Minimum required:
2-4 core contributions or innovation pointsStrongly recommended:
If any required field is missing, do not output a fake journal-ready letter. Use this structure first:
Cannot finalize the cover letter yet.
Missing required items:
- <item 1>
- <item 2>
Usable fallback:
- I can draft a partial letter shell after these items are supplied.Only draft a partial shell if the user explicitly wants one after seeing the missing items.
Return a complete letter using the structure below:
Formatting rules:
4-6 short paragraphsgroundbreaking, revolutionary, or game-changingConfirm that all required items are present.
If not:
## Missing-Input RecoveryWrite 1-2 sentences that connect:
Avoid generic fit claims like This paper will interest your readers unless followed by a concrete reason.
Summarize:
Keep this focused on contributions, not full manuscript retelling.
Use only concise, high-signal evidence:
Do not turn this section into a mini-abstract.
Always include or explicitly request:
Add journal-specific statements if the user supplies them:
Use the following logic:
If the user does not provide a declaration that may be required, ask for it rather than inventing it.
assets/cover_letter_template.md as the paragraph skeleton.references/guide.md as the preflight checklist.Before returning the letter, verify:
e1f6461
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.