cover-letter-generator

Create personalized, compelling cover letters from resume and job description

Quality

33%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/cover-letter-generator/SKILL.md

Quality

Discovery

40%

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 niche (cover letter generation from resume and job description) which makes it distinctive, but it lacks explicit trigger guidance ('Use when...') and could benefit from more specific capability details and keyword variations. The single-action description is too brief to fully inform skill selection among many options.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to write or draft a cover letter, application letter, or needs help applying for a job.'

Include common keyword variations such as 'application letter', 'CV', 'job posting', 'job listing', 'job application' to improve trigger term coverage.

Expand the capability list with specific actions like 'tailors experience highlights to job requirements, matches tone to company culture, formats professionally'.

Dimension	Reasoning	Score
Specificity	Names the domain (cover letters) and mentions key inputs (resume and job description), but only describes one action ('create') without listing specific sub-capabilities like tailoring tone, highlighting relevant experience, formatting, etc.	2 / 3
Completeness	Describes what it does (create cover letters from resume and job description) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes natural terms like 'cover letters', 'resume', and 'job description' which users would likely say, but misses common variations like 'application letter', 'CV', 'job posting', 'job listing', or 'cover letter writing'.	2 / 3
Distinctiveness Conflict Risk	The combination of cover letters + resume + job description creates a clear, specific niche that is unlikely to conflict with other skills. This is a well-defined use case distinct from general writing or resume-building skills.	3 / 3
	Total	8 / 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 reads more like a comprehensive blog post or writing guide about cover letters than a concise skill file for Claude. The vast majority of the content—what makes a good cover letter, hook strategies, tone advice, do's and don'ts—is general knowledge Claude already possesses. The skill would be far more effective as a short configuration file specifying the desired output format, quality checklist, and any project-specific conventions, with the extensive examples and scenarios moved to reference files or eliminated entirely.

Suggestions

Reduce content by 70-80%: Remove all general cover letter writing advice Claude already knows (philosophy, why generic letters are bad, basic formatting) and focus only on the specific output format, quality checklist, and any non-obvious constraints.

Split remaining content: Move industry-specific considerations, common scenarios, and hook examples into separate reference files (e.g., SCENARIOS.md, EXAMPLES.md) and link to them from a concise overview.

Add an explicit workflow with validation: Define a clear numbered sequence (e.g., 1. Read resume, 2. Analyze JD, 3. Identify top 3 matches, 4. Draft letter, 5. Validate against checklist, 6. Revise if needed) with explicit checkpoints.

Clarify the dependency on JD analysis: Specify exactly what inputs this skill expects (e.g., match score, key requirements list) and how they feed into the cover letter generation, rather than vaguely saying 'Use AFTER analyzing job description.'

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~250+ lines. Explains concepts Claude already knows well (what makes a good cover letter, why generic letters are bad, basic letter formatting). The 'philosophy' section, extensive lists of do's/don'ts, and multiple hook examples are things Claude can generate without instruction. Most of this content is general writing advice rather than novel, actionable configuration.	1 / 3
Actionability	Provides concrete examples and templates which are useful, but they're illustrative rather than executable—there's no code, no tool usage, no specific commands. The examples are fill-in-the-blank templates with placeholders rather than truly copy-paste ready artifacts. The output format section is reasonably specific and actionable.	2 / 3
Workflow Clarity	There's a clear sequence implied (analyze JD → identify matches/gaps → write letter → check quality), and the quality checklist at the end serves as a validation step. However, the workflow is not explicitly sequenced with numbered steps and validation checkpoints. The relationship between JD analysis (referenced as a prerequisite) and this skill is mentioned but not clearly defined with feedback loops.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files despite the content being long enough to warrant splitting. Industry-specific considerations, common scenarios, and the extensive examples could all be in separate reference files. Everything is inlined in one massive document with no bundle files to support it.	1 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: paramchoudhary/resumeskills
Commit: 24c6edc

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.