CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cover-letter-generator

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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/cover-letter-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction skill with an explicit validated workflow, but it is held back by redundancy (missing-input and out-of-scope handling repeated across three sections) and by two referenced bundle files that do not exist. Fixing the dangling template and checklist references would materially improve both actionability and navigation.

Suggestions

Ship the referenced files or remove the references: `assets/cover_letter_template.md` and `references/guide.md` are named in "Templates and Assets" but neither exists in the bundle, so the paragraph skeleton and preflight checklist can never be used.

Consolidate the three overlapping guard sections ("Missing-Input Recovery", "Error Handling", "Input Validation") into one section — they each restate the same stop-and-request-missing-inputs behavior, and merging them would cut significant tokens.

Fold the "Quality Checklist" items into the Drafting Workflow steps or the Output Contract, since each checklist line already appears as a rule elsewhere in the body.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and stays on-task, but it repeats the same control logic in multiple sections: missing-input handling appears in "Missing-Input Recovery", again in "Error Handling" ("state exactly which fields are missing and request only the minimum additional information"), and again in "Input Validation"; the "Quality Checklist" restates constraints already given in the Output Contract and Drafting Workflow. This is a mostly-efficient document that could be consolidated, not noticeably padded with irrelevant explanation, so it sits at the middle anchor rather than the verbose one below.

3 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: enumerated required inputs, a verbatim copy-paste response template for missing inputs, a 9-part ordered Output Contract, and a journal-type declaration matrix. It falls short of fully-executable because there is no worked example letter showing the common case, and the referenced template skeleton is only named, not provided inline.

4 / 5

Workflow Clarity

The Drafting Workflow is a clearly sequenced five-step process that begins with explicit input validation, routes failures into the Missing-Input Recovery checkpoint with a stop-before-drafting gate and a user-confirmation feedback loop ("Only draft a partial shell if the user explicitly wants one"), and ends with a pre-return Quality Checklist. This matches the anchor for clear sequence, explicit validation, error-recovery feedback, and a checklist; there are no gaps that would drop it to 4.

5 / 5

Progressive Disclosure

The body is well-sectioned and its two references ("Use `assets/cover_letter_template.md` as the paragraph skeleton" and "Use `references/guide.md` as the preflight checklist") are clearly signaled — but no `assets/` or `references/` directories exist in the bundle, so both are dangling pointers that break navigation when followed. Structure and organization are present, but the missing referenced files keep this below the good-structure anchor; it is above anchor 2 because the body itself is not a minimal or unstructured wall of text.

3 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete inputs and output, and an explicit, specific 'Use when' trigger clause tied to academic submission preparation. Its only weaknesses are minor missing trigger synonyms and a slight collision risk with non-academic cover letter requests.

DimensionReasoningScore

Specificity

"Generates a journal-ready cover letter from manuscript metadata, highlights, and journal-fit notes" names the domain and one concrete action with its inputs, plus the editorial elements it states ("novelty, relevance, declarations, and corresponding-author details"). This matches the anchor for naming the domain with 1-2 concrete actions but not comprehensive coverage; it is not the level above because it describes a single action rather than several distinct capabilities.

3 / 5

Completeness

It explicitly answers both questions: the "what" is "Generates a journal-ready cover letter from manuscript metadata, highlights, and journal-fit notes" and the "when" is the explicit "Use when" clause "preparing an academic submission package and you need editor-facing language that clearly states novelty, relevance, declarations, and corresponding-author details". Both are concrete with explicit trigger phrases; it is not score 4 because the when-clause is already specific, not merely present.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: "cover letter", "manuscript", "academic submission package", "journal", "declarations", "corresponding-author" — all things a user preparing a submission would actually say. A few natural variants are missing (e.g., "submission letter", "manuscript submission"), which fits the good-coverage-with-gaps anchor rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"journal-ready", "manuscript metadata", "academic submission package", "corresponding-author details" carve out a clear editor-facing academic niche distinct from general writing skills. Minor overlap risk remains with job-application cover letters ("help me write a cover letter"), so it is mostly distinct rather than a clear niche with minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/cover-letter-generator/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.