resume-ats-optimizer

Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match

Quality

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/resume-ats-optimizer/SKILL.md

Quality

Discovery

67%

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 is strong in specificity and distinctiveness, clearly naming concrete actions within a well-defined niche of ATS resume optimization. Its main weaknesses are the absence of an explicit 'Use when...' clause and missing some natural trigger terms users might employ when seeking this skill.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about resume optimization, ATS scoring, job application keywords, or resume compatibility checks.'

Include additional natural trigger terms like 'job application', 'resume review', 'resume scan', 'job posting match', or 'resume keywords' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Optimize resumes for Applicant Tracking Systems', 'check ATS compatibility', and 'analyze keyword match'. These are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with three specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes good terms like 'resumes', 'ATS', 'Applicant Tracking Systems', 'keyword match', and 'ATS compatibility'. However, it misses common user variations like 'job application', 'resume review', 'resume keywords', 'job posting', or 'resume scan'.	2 / 3
Distinctiveness Conflict Risk	The combination of ATS, resume optimization, and keyword matching creates a very clear niche that is unlikely to conflict with other skills. The domain is specific and well-defined.	3 / 3
	Total	10 / 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 reads more like a comprehensive blog post about ATS optimization than a concise, actionable skill for Claude. It contains significant amounts of general knowledge Claude already possesses (what ATS is, why resumes fail, industry-specific advice) while lacking executable tooling, validation checkpoints, and proper content organization. The structured output format and keyword placement strategy are useful, but they're buried in excessive explanatory content.

Suggestions

Cut 'The ATS Problem' section entirely and trim industry-specific/edge case sections — Claude already knows this context. Focus the skill on the analysis output format, keyword matching process, and implementation checklist.

Add validation checkpoints to the workflow: e.g., 'Confirm resume text was successfully extracted before proceeding to keyword analysis' and 'If match score is below 80%, iterate on keyword placement before presenting final report.'

Split industry-specific considerations, edge cases, and common failure patterns into separate referenced files to reduce the main skill to a concise overview with clear navigation.

Provide executable code or concrete tool-use instructions for resume parsing and keyword extraction rather than describing the process abstractly.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Explains concepts Claude already knows (what ATS is, why companies use them, that 75% of resumes are rejected). Sections like 'The ATS Problem', industry-specific considerations, and edge cases are general knowledge padding that don't add actionable value. Much of this content is resume advice for humans, not instructions for Claude.	1 / 3
Actionability	Provides concrete checklists, a structured output format, and specific before/after examples for keyword placement. However, there's no executable code or tooling despite the description mentioning 'parse resume' and 'calculate match scores' — the match score formula is trivial arithmetic, not a real implementation. The guidance is more of a knowledge dump than precise instructions Claude can execute.	2 / 3
Workflow Clarity	The keyword optimization process has a clear 4-step sequence and the implementation checklist provides ordering. However, there are no validation checkpoints or feedback loops — no step says 'verify parsing succeeded before proceeding' or 'if match score is below threshold, iterate on these specific areas.' The re-scoring step (step 8) is listed but not elaborated with error recovery.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content — from basic ATS concepts to industry-specific advice to edge cases — is crammed into a single file. Industry-specific sections, edge cases, and common failure patterns could easily be split into referenced files. No bundle files exist to support progressive disclosure.	1 / 3
	Total	6 / 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
Commit: 24c6edc

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