cover-letter-drafter
Generates professional cover letters for journal submissions and job.
43
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—the sentence appears truncated after 'and job'. It lacks a 'Use when...' clause, specific concrete actions, and sufficient trigger term coverage to reliably distinguish it from other writing-related skills.
Suggestions
Complete the truncated sentence and add a 'Use when...' clause, e.g., 'Use when the user asks for a cover letter, application letter, or submission letter for jobs or academic journals.'
Add specific actions such as 'tailors content to job descriptions, highlights relevant qualifications, formats for academic or professional standards.'
Include natural trigger term variations like 'application letter', 'manuscript submission cover letter', 'job application', and 'hiring'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cover letters) and two contexts (journal submissions and job), but doesn't list specific concrete actions like drafting, formatting, tailoring to job descriptions, or highlighting qualifications. | 2 / 3 |
Completeness | Describes what it does (generates cover letters) but has no explicit 'Use when...' clause or trigger guidance, and the description appears truncated ('for journal submissions and job' seems incomplete). Per rubric, missing 'Use when' caps completeness at 2, and the incomplete sentence further reduces it. | 1 / 3 |
Trigger Term Quality | Includes some natural keywords like 'cover letters', 'journal submissions', and 'job', but misses common variations such as 'application letter', 'job application', 'manuscript submission', 'hiring', or 'resume'. | 2 / 3 |
Distinctiveness Conflict Risk | Cover letters for journal submissions and jobs is a reasonably specific niche, but could overlap with general writing/document generation skills or resume-building skills without clearer trigger terms. | 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 is heavily padded with generic boilerplate (risk assessment, security checklist, lifecycle status, evaluation criteria, response template) that adds no cover-letter-specific value and wastes significant token budget. The useful content—parameter table, usage examples, and output format—is buried among repetitive and circular sections. The skill would benefit enormously from cutting 60-70% of the content and focusing on the concrete, actionable parts.
Suggestions
Remove all generic boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template, Output Requirements) that don't contain cover-letter-specific guidance.
Eliminate circular self-references ('See ## Features above', 'See ## Usage above') and consolidate duplicated content into a single coherent flow.
Consolidate the workflow into one clear numbered sequence that includes a validation step for reviewing the generated cover letter quality before returning it to the user.
Keep only the Parameters table, Usage examples, Output Format, and a brief Quick Start section—these are the actionable parts that earn their token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. Multiple sections reference each other circularly ('See ## Features above', 'See ## Prerequisites above', 'See ## Usage above'). Boilerplate sections like Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, and Response Template add significant token bloat without providing actionable value for generating cover letters. Much content is generic template filler not specific to this skill. | 1 / 3 |
Actionability | The Usage section provides concrete, executable command examples with specific flags for journal, job, and fellowship cover letters, and the Parameters table is well-defined. However, much of the 'Implementation Details' and 'Workflow' sections are abstract and generic rather than specific to cover letter generation. The actual script behavior is opaque—there's no indication of what the script does internally. | 2 / 3 |
Workflow Clarity | There is a numbered workflow and an 'Example run plan' with steps, but they are generic and duplicative. The error handling section mentions fallback paths but doesn't specify concrete validation checkpoints (e.g., validating the generated cover letter content). No feedback loop for reviewing output quality before finalizing. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with many sections that could be consolidated or removed. Circular self-references ('See ## Features above') add confusion rather than navigation. There are references to 'references/' directory but no specific file links. The document has ~15+ sections when 4-5 well-organized ones would suffice. | 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 | |
- Repository
- aipoch/medical-research-skills
- Commit
8277276
- 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.