Menu

Individual skill

journal-cover-letter-skill

0upvotes

Create, revise, benchmark, or check a cover letter for an academic journal submission from manuscript files. Use whenever a user wants a journal submission letter, asks to tailor a cover letter to a target journal, provides manuscript materials and asks for a letter, wants an existing academic cover letter improved, or submits a bibliometric/science-mapping manuscript. Route empirical research around one finding, evidence syntheses around what the synthesis changes in understanding, and bibliometric studies around what the map reveals about a field's structure or evolution. Do not use for job applications, recommendation letters, or business correspondence.

skills/journal-cover-letter-skill/SKILL.md

Read pinned source

Source commit b1f2fc9e24ef2effd2e6abdf3ef3f2daaac77757

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
42
Repository last updated
Oct 1, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Journal Cover Letter Skill v3.2

Turn verified manuscript facts into a clear editorial decision aid. Default to English unless the user requests another language. Prioritize biomedical and life-science submissions while remaining useful across disciplines.

## Core architecture: evidence anchor -> editorial meaning

Every persuasive claim must contain both parts:

- `empirical_anchor`: the concrete, manuscript-traceable observation selected for the editor;
- `editorial_meaning`: what that observation changes in understanding, interpretation, coordination, practice, or the next research decision.

For manuscripts with a distinctive empirical taxonomy, trend set, or named result pattern, also preserve an `authorial_empirical_fingerprint`: the minimum manuscript-native detail that lets an editor distinguish this paper from another paper on the same topic.

A letter fails when it offers facts without meaning, meaning without a traceable factual anchor, or a polished abstraction that erases the manuscript's empirical fingerprint. This is the central v3.1 rule.
Back to top