tailored-resume-generator
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill tailored-resume-generator49
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
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 communicates the core purpose of resume tailoring but lacks explicit trigger guidance ('Use when...') which is critical for skill selection. It has moderate specificity and trigger terms but would benefit from more concrete actions and natural keyword variations users might employ when seeking this functionality.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to create a resume, tailor a CV, apply for a job, or match their experience to a job posting'
Include common keyword variations users might say: 'CV', 'job application', 'job posting', 'career', 'apply for position'
Add more specific concrete actions: 'rewrites bullet points', 'matches keywords from job postings', 'formats resume sections', 'quantifies achievements'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (job descriptions, resumes) and some actions (analyzes, generates, highlight), but lacks comprehensive specific actions like 'formats sections', 'rewrites bullet points', or 'matches keywords'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'job descriptions', 'resumes', 'experience', 'skills', 'achievements', and 'interview', but missing common variations users might say like 'CV', 'cover letter', 'job application', 'job posting', or 'career'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to resume/job description domain, but could overlap with general writing skills, career advice skills, or document formatting skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable guidance with excellent concrete examples, but suffers from severe verbosity and poor organization. It explains many concepts Claude already knows (resume basics, ATS systems, action verbs) and presents everything in a single massive file rather than using progressive disclosure. The workflow is clear but lacks validation checkpoints.
Suggestions
Remove sections explaining concepts Claude already knows: 'When to Use This Skill', 'What This Skill Does', basic resume writing advice, and standard formatting guidelines
Split content into separate files: move 'Special Considerations' (career changers, executives, etc.) to SPECIAL_CASES.md and 'Best Practices' to a reference file
Add validation checkpoints: after generating resume, explicitly verify keyword coverage against job requirements and check for quantified achievements
Condense the main skill to ~50-75 lines focusing on the core workflow: gather info → analyze requirements → map experience → generate tailored resume
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 300+ lines. Explains obvious concepts Claude already knows (what ATS is, how to use action verbs, basic resume structure). Sections like 'When to Use This Skill' and 'What This Skill Does' are unnecessary meta-descriptions. The 'Best Practices' and 'Special Considerations' sections explain standard resume writing knowledge. | 1 / 3 |
Actionability | Provides concrete, executable guidance with a complete example showing input and full output resume. The step-by-step instructions are specific with exact formatting patterns, bullet point structures, and clear templates to follow. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered (1-10) with logical sequence, but lacks validation checkpoints. No explicit verification steps to confirm the tailored resume matches requirements or to catch errors before presenting to user. Missing feedback loops for quality assurance. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed special considerations, best practices, and extensive examples that could be split into separate reference documents. No navigation structure for a 300+ line skill. | 1 / 3 |
Total | 7 / 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 | |
- 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.