Content
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 a comprehensive cover letter writing guide but suffers significantly from verbosity — it reads more like a blog post or tutorial than a concise skill instruction for Claude. It explains many concepts Claude already understands (what makes a good cover letter, why generic openings are bad) and packs everything into a single monolithic file. The examples and templates provide some actionable value, but the overall token cost is far too high for the incremental knowledge it provides.
Suggestions
Cut the content by 60-70%: remove the 'Cover Letter Philosophy' section, 'Opening Don'ts'/'Closing Don'ts' lists, and industry-specific considerations — Claude already knows these. Focus on the specific template, output format, and quality checklist.
Split detailed examples (hook types, scenario handling, industry considerations) into separate reference files like EXAMPLES.md and SCENARIOS.md, keeping SKILL.md as a lean overview with clear links.
Add explicit workflow steps: 1) Read resume, 2) Analyze JD requirements, 3) Identify top 3 qualification matches, 4) Check for gaps, 5) Select hook type, 6) Generate letter, 7) Validate against checklist — with clear sequencing and validation checkpoints.
Remove explanatory framing like 'The Problem/The Solution' and 'The opening is critical - you have 5 seconds to grab attention' — these add no actionable value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Extensively explains cover letter philosophy, what makes a good cover letter, and general writing advice — all things Claude already knows well. The 'Opening Don'ts', 'Closing Don'ts', hook type explanations, and industry-specific considerations are largely common knowledge for Claude. Very few tokens here earn their place. | 1 / 3 |
Actionability | Provides concrete examples of openings, body paragraphs, and closings with templates, which is helpful. However, these are illustrative text snippets rather than executable code/commands. The guidance is specific but the skill is more of a writing guide than a precise, actionable instruction set — it describes good practices rather than giving Claude a tight algorithm to follow. | 2 / 3 |
Workflow Clarity | There is a clear structure (opening → body 1 → body 2 → closing) and a quality checklist at the end, which provides some validation. However, the actual workflow for generating a cover letter (analyze JD first, gather resume data, match qualifications, then write) is only loosely implied. The reference to 'Use AFTER analyzing job description' and 'Match Score: [From JD Analyzer]' suggests dependencies on other skills but doesn't clearly sequence the full process. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files. All content — philosophy, examples, templates, industry considerations, scenario handling — is crammed into a single massive document. Much of this content (industry-specific tips, common scenarios) could be split into separate reference files. | 1 / 3 |
Total | 6 / 12 Passed |