Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
61
42%
Does it follow best practices?
Impact
96%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/tailored-resume-generator/SKILL.mdQuality
Discovery
57%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 communicates a clear purpose—analyzing job descriptions and generating tailored resumes—which gives it a distinct niche. However, it lacks an explicit 'Use when...' clause and could benefit from more specific concrete actions and additional natural trigger terms users might use (e.g., 'CV', 'job application', 'ATS').
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, tailor, or update a resume for a specific job posting or role.'
Include additional natural trigger terms users might say, such as 'CV', 'job application', 'ATS optimization', 'career', or 'cover letter'.
List more specific concrete actions, e.g., 'extracts keywords from job postings, maps experience to requirements, formats resume sections, optimizes for ATS compatibility'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (resumes/job descriptions) and some actions (analyzes, generates, highlight), but doesn't list multiple concrete specific actions like formatting, section creation, keyword optimization, or ATS compatibility. | 2 / 3 |
Completeness | Clearly answers 'what' (analyzes job descriptions and generates tailored resumes), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps this at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'job descriptions', 'resumes', 'experience', 'skills', 'achievements', and 'interview', but misses common variations users might say such as 'CV', 'cover letter', 'job application', 'tailor resume', or 'ATS'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of job description analysis and tailored resume generation is a clear, specific niche that is unlikely to conflict with other skills. The focus on resume tailoring to job descriptions is quite distinct. | 3 / 3 |
Total | 9 / 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 extremely verbose, containing extensive resume-writing advice that Claude already knows, inflating the token cost significantly without proportional value. The full input/output example is a genuine strength, but the surrounding content reads more like a comprehensive human guide than a focused skill for an AI assistant. The lack of progressive disclosure and validation checkpoints further weakens the skill.
Suggestions
Cut the content by 60-70%: remove 'When to Use,' 'What This Skill Does,' 'Tips for Best Results,' 'Privacy Note,' and most of 'Best Practices' — Claude already knows standard resume conventions.
Extract 'Special Considerations' (career changers, graduates, executives, etc.) into a separate SCENARIOS.md file and reference it from the main skill.
Add explicit validation checkpoints in the workflow, e.g., 'Verify all Priority 1 requirements from the job description are addressed before presenting the resume' and 'Cross-check that key ATS keywords appear in the output.'
Replace the descriptive instruction style with more directive, concise commands — e.g., instead of explaining what action verbs are, just say 'Use strong action verbs; quantify all achievements with metrics.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains concepts Claude already knows well (what ATS is, how to write bullet points, what action verbs are, basic resume formatting conventions). Sections like 'Best Practices,' 'Special Considerations,' and 'Tips for Best Results' are largely common knowledge for Claude. The 'When to Use This Skill' and 'What This Skill Does' sections are unnecessary preamble. | 1 / 3 |
Actionability | The full example with input and output is genuinely useful and concrete. However, much of the instruction content is descriptive rather than executable — it reads more like a guide for a human than precise instructions for Claude. There are no code snippets, tool invocations, or structured output schemas; the 'instructions' are largely general resume-writing advice. | 2 / 3 |
Workflow Clarity | The 10-step numbered workflow provides a clear sequence, and step 8 includes iteration. However, there are no validation checkpoints — no step to verify keyword match percentage, no explicit check that all must-have requirements are addressed, and no feedback loop for catching errors or omissions before presenting the final resume. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. The 'Special Considerations' section alone (career changers, graduates, executives, technical, creative) could easily be split into separate reference files. Everything is inlined in one massive document with no navigation aids or cross-references. | 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 | |
7cc63f3
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.