resume-version-manager

Track different resume versions, maintain master resume, manage tailored versions

Quality

30%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/resume-version-manager/SKILL.md

Quality

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 excessively verbose, explaining concepts and organizational strategies that Claude already understands, while lacking truly executable or automatable guidance. The content reads more like a blog post or career advice article than a concise skill instruction. The structure is entirely monolithic with no progressive disclosure, and workflows lack validation checkpoints.

Suggestions

Cut content by 60-70%: remove explanations of what a master resume is, the pain points section, the version categories by industry/seniority (Claude knows these), and the common scenarios section. Focus only on the specific system/conventions to follow.

Add executable actions: include actual commands or scripts for creating folder structures, renaming files, or generating tracker entries rather than just describing them conceptually.

Split into multiple files: move the master resume template, application tracker template, and naming convention reference into separate referenced files to enable progressive disclosure.

Add validation checkpoints to the workflow: e.g., verify naming convention compliance, check that tailored version doesn't exceed page limit, confirm tracker was updated before marking complete.

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 checklists and scenarios that pad the content without adding actionable value Claude couldn't infer.	1 / 3
Actionability	Provides concrete folder structures, naming conventions, and a tracker spreadsheet format, which are useful. However, there are no executable commands or scripts—everything is descriptive markdown templates and conceptual workflows rather than automatable steps. The 'Master to Tailored Workflow' is a numbered list of abstract actions, not concrete executable guidance.	2 / 3
Workflow Clarity	The 'Master to Tailored Workflow' provides a clear sequence of steps, and the update triggers are well-defined. However, there are no validation checkpoints—no step to verify the tailored version actually matches the job description keywords, no check that the naming convention was followed, and no feedback loop for catching errors in the process.	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 a single massive document. Much of this could be split into referenced files (e.g., naming conventions, tracker templates, category guides).	1 / 3
	Total	6 / 12 Passed

Description

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 like 'track', 'maintain', and 'manage' without specifying concrete operations. It critically lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. Adding explicit trigger guidance and more specific actions would significantly improve its effectiveness.

Suggestions

Add a 'Use when...' clause with trigger terms like 'resume', 'CV', 'job application', 'tailor resume for', 'customize resume'.

Replace vague verbs with concrete actions, e.g., 'Create tailored resume versions from a master resume, compare differences between versions, export resumes for specific job applications'.

Include common keyword variations such as 'CV', 'curriculum vitae', 'job-specific resume', and 'resume customization' 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 the rubric, a missing 'Use when...' clause 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 'resume for [company]'.	2 / 3
Distinctiveness Conflict Risk	The resume domain is fairly specific and unlikely to conflict with most other skills, but 'version tracking' and 'manage' are generic enough that it could overlap with general file management or version control skills.	2 / 3
	Total	7 / 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
Path: skills/resume-version-manager/SKILL.md
Commit: 74ae19e

Reviewed: about 13 hours 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.