resume-version-manager
Track different resume versions, maintain master resume, manage tailored versions
35
30%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/resume-version-manager/SKILL.mdQuality
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 identifies a clear domain (resume management) but relies on vague verbs and lacks explicit trigger guidance. It would benefit from more concrete action descriptions and a 'Use when...' clause to help Claude distinguish this skill from general document or version management skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when the user asks about resume versions, tailoring a resume for a job posting, updating their CV, or managing multiple resume variants'.
Replace vague verbs with concrete actions, e.g., 'Create tailored resume versions from a master template, compare resume drafts, merge updates across versions, export resumes for specific job applications'.
Include common synonyms and variations such as 'CV', 'curriculum vitae', 'job application', 'customize resume' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (resume management) and some actions (track versions, maintain master, manage tailored versions), but the actions are somewhat vague—'track', 'maintain', and 'manage' are generic verbs that don't describe concrete operations like 'create', 'diff', 'merge', or 'export'. | 2 / 3 |
Completeness | Describes what the skill does (track/maintain/manage resume versions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'resume', 'versions', 'master resume', and 'tailored versions' which users might naturally say, but misses common variations like 'CV', 'job application', 'customize resume', or file format references. | 2 / 3 |
Distinctiveness Conflict Risk | The resume-specific focus provides some distinctiveness, but 'track versions' and 'manage' are generic enough to potentially overlap with general version control or document management skills. | 2 / 3 |
Total | 7 / 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 excessively verbose, explaining concepts and organizational strategies that Claude already understands (what a master resume is, common pain points, industry tone differences). While it provides some useful templates like folder structures and naming conventions, the content is largely descriptive rather than actionable, and the monolithic structure makes it inefficient as a context-window resource. The skill would benefit enormously from being reduced to ~50 lines of core templates and conventions.
Suggestions
Reduce content by 70-80%: remove explanations of what a master resume is, pain points, version categories by industry/seniority (Claude knows these), and focus only on the specific templates, naming conventions, and workflow steps.
Split into multiple files: keep SKILL.md as a concise overview with the naming convention and workflow, then reference separate files for master resume template, folder structure, and application tracker template.
Add validation checkpoints to the workflow: e.g., 'Verify tailored version contains at least 60% of job description keywords' or 'Confirm file saved with correct naming convention before updating tracker.'
Make the output format more actionable by providing a concrete example with real sample data rather than placeholder brackets throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains obvious concepts like what a master resume is, lists common pain points Claude doesn't need, describes version categories by industry/seniority that are general knowledge, and includes extensive DO/DON'T lists that are common sense. Very little of this content adds knowledge Claude doesn't already possess. | 1 / 3 |
Actionability | Provides concrete folder structures, naming conventions, and a tracker spreadsheet format, which are useful templates. However, there's no executable code or tool-based commands—it's all markdown templates and conceptual workflows. The 'Master to Tailored Workflow' is a numbered list of general steps rather than specific, executable guidance. | 2 / 3 |
Workflow Clarity | The 'Master to Tailored Workflow' provides a clear 10-step sequence, and update triggers are specified. However, there are no validation checkpoints—no step to verify the tailored version actually matches the job description keywords, no check that the file was saved correctly, and no feedback loop for error recovery. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—master resume structure, folder organization, version categories by role/industry/seniority, application tracking, scenarios, checklists—is inlined in one massive document. Much of this could be split into separate reference files (e.g., naming conventions, tracker templates, category guides). | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%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
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.