Generates professional cover letters for journal submissions and job.
43
Quality
30%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/cover-letter-drafter/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (cover letter generation) but is incomplete and lacks specificity. The truncated 'job' suggests an editing error, and the absence of explicit trigger guidance significantly limits Claude's ability to know when to select this skill. Adding concrete actions and a 'Use when...' clause would substantially improve selection accuracy.
Suggestions
Add a 'Use when...' clause with trigger terms like 'cover letter', 'job application', 'manuscript submission', 'applying for', 'journal cover letter'
Complete the truncated phrase 'job' to 'job applications' and add specific actions like 'tailors content to position requirements', 'formats for academic or professional contexts'
Include natural keyword variations users might say: 'application letter', 'submission letter', 'CV cover', 'applying to journals'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cover letters) and specifies two contexts (journal submissions and job), but lacks concrete actions like 'drafts', 'tailors to job requirements', or 'formats according to academic standards'. | 2 / 3 |
Completeness | Describes what it does (generates cover letters) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'cover letters', 'journal submissions', and 'job' which are relevant keywords, but missing common variations like 'application letter', 'CV cover', 'manuscript submission', or 'job application'. | 2 / 3 |
Distinctiveness Conflict Risk | Cover letters for journal submissions is somewhat specific, but 'job' is truncated/incomplete and the description could overlap with general writing or document generation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers from severe bloat and poor organization. The useful content (CLI parameters, example commands, output format) is buried under layers of generic boilerplate including security checklists, risk assessments, and circular cross-references. The skill tells you how to run a script but doesn't actually teach cover letter writing or provide domain-specific guidance.
Suggestions
Remove all circular cross-references ('See ## Features above') and consolidate duplicated sections (Usage appears twice, Prerequisites mentioned multiple times)
Delete generic boilerplate sections (Security Checklist, Risk Assessment, Lifecycle Status, Evaluation Criteria) that don't add cover-letter-specific value
Add actual cover letter guidance: what makes a good journal submission letter vs job application, common mistakes to avoid, example output showing quality expectations
Describe what's in the 'references/' folder and how templates can be customized for different letter types
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with massive redundancy - multiple sections reference each other circularly ('See ## Features above', 'See ## Prerequisites above'), boilerplate security checklists, risk assessments, and lifecycle status that add no value. The actual cover letter generation guidance is buried under excessive scaffolding. | 1 / 3 |
Actionability | Provides concrete CLI examples with specific flags and parameters, which is good. However, the actual script behavior is opaque - no indication of what the script does internally, what templates look like, or how to customize output quality. The examples are copy-paste ready but the skill doesn't teach how to write better cover letters. | 2 / 3 |
Workflow Clarity | Has a numbered workflow section but it's generic boilerplate applicable to any skill, not specific to cover letter drafting. No validation of cover letter quality, no feedback loop for improving output, no guidance on reviewing generated letters for appropriateness. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with poor organization - sections reference each other circularly, content is duplicated across sections (Usage appears twice, Prerequisites mentioned multiple times), and there's no clear hierarchy. References to 'references/' folder without explaining what's there. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4a48721
Table of Contents
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.