cover-letter-drafter
Generates professional cover letters for journal submissions and job applications in medical and academic contexts.
Install with Tessl CLI
npx tessl i github:aipoch/medical-research-skills --skill cover-letter-drafterOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 (academic/medical cover letters) but lacks the explicit trigger guidance essential for skill selection. It provides moderate specificity about the output type but doesn't detail concrete actions or include a 'Use when...' clause, making it harder for Claude to confidently select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs help writing cover letters for journal manuscript submissions, faculty positions, residency applications, or academic job applications.'
Include more natural trigger term variations users might say: 'manuscript submission letter', 'faculty cover letter', 'residency application letter', 'academic job letter'.
List specific concrete actions: 'Formats professional cover letters, tailors content to position requirements, highlights relevant publications and experience, follows academic conventions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cover letters for journal submissions and job applications) and context (medical and academic), but doesn't list specific concrete actions like 'formats sections', 'tailors to job requirements', or 'includes publication highlights'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'cover letters', 'journal submissions', 'job applications', 'medical', 'academic', but missing common variations users might say like 'CV cover letter', 'manuscript submission letter', 'faculty application', or 'residency application'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'journal submissions' and 'medical/academic contexts' provides some specificity, but 'cover letters' and 'job applications' are broad enough to potentially overlap with general writing or career-focused skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides clear, actionable CLI examples with well-defined parameters and output format. However, it's padded with boilerplate sections (risk assessment, security checklist, evaluation criteria) that don't help Claude execute the task, and it lacks guidance on cover letter quality standards or how to iterate on generated output.
Suggestions
Remove or significantly trim boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't aid task execution
Add brief guidance on what makes an effective cover letter for each purpose type (journal vs job vs fellowship)
Include a validation step or quality checklist for reviewing generated cover letters before finalizing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes substantial boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add little value for Claude's task execution. The core usage examples are efficient, but the document is padded with template content. | 2 / 3 |
Actionability | Provides fully executable command-line examples for all three use cases (journal, job, fellowship) with specific parameters. The output JSON format is clearly specified and copy-paste ready. | 3 / 3 |
Workflow Clarity | This is a single-command tool with clear usage, but lacks guidance on what makes a good cover letter, how to verify output quality, or what to do if the generated letter needs refinement. No validation or iteration workflow is provided. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but includes inline boilerplate (security checklist, lifecycle status) that could be omitted or referenced elsewhere. No references to external files for templates or examples. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%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 | |
- 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.