job-description-analyzer

Analyze job postings, calculate match scores, identify gaps, and create application strategy

Quality

30%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/job-description-analyzer/SKILL.md

Quality

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 names a reasonable set of actions related to job application analysis but lacks a 'Use when...' clause, which is a significant omission for skill selection. It also misses common user-facing trigger terms like 'resume', 'job search', and 'career', reducing its discoverability. Adding explicit trigger guidance and more natural keywords would substantially improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to evaluate a job posting against their resume, assess job fit, or plan a job application strategy.'

Include natural trigger terms users would say, such as 'resume', 'job search', 'job fit', 'career', 'qualifications', 'job description', and 'cover letter'.

Make capabilities more concrete, e.g., 'Compare resume skills against job requirements, calculate a fit score, highlight missing qualifications, and suggest tailored application tactics.'

Dimension	Reasoning	Score
Specificity	Lists several actions (analyze job postings, calculate match scores, identify gaps, create application strategy) but they remain somewhat high-level without specifying concrete mechanisms like 'compare resume skills to job requirements' or 'generate tailored cover letter points'.	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 the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'job postings', 'match scores', 'application strategy', and 'gaps', but misses common user phrases like 'resume', 'job search', 'job application', 'career', 'job fit', or 'qualifications'.	2 / 3
Distinctiveness Conflict Risk	The combination of job posting analysis and match scoring is somewhat distinctive, but 'application strategy' and 'identify gaps' are broad enough to overlap with general career coaching or resume review 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 far too verbose, inlining a massive example output template and extensive explanatory content that Claude doesn't need. While the analysis framework is reasonably well-structured with clear steps and a useful match calculation approach, the content would benefit enormously from splitting the output template and reference lists into separate files. The skill explains too many concepts Claude already understands (what red flags are, how job seeking works) rather than focusing on precise, actionable instructions.

Suggestions

Extract the ~150-line example output into a separate TEMPLATE.md file and reference it from SKILL.md, reducing the main file to a concise overview

Remove the 'Strategic Problem' section entirely — Claude doesn't need a lecture on why strategic job applications matter; just instruct it to calculate and recommend

Move the 'Requirement Classification Guide', 'Red Flag Detection' lists, and 'Edge Cases' into a separate REFERENCE.md file to improve progressive disclosure

Add validation checkpoints: verify user has provided both a job description AND their experience/resume before proceeding with match calculation; handle missing input gracefully

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Explains obvious concepts like what red flags mean, how to classify requirements (language Claude already understands), and includes a massive example output that could be a template reference. The 'Strategic Problem' section lectures about job seeking strategy which is unnecessary context for Claude.	1 / 3
Actionability	Provides a concrete match calculation formula and a detailed output template, which are useful. However, there's no executable code, no actual tool usage, and the match calculation is pseudocode-level arithmetic rather than a real algorithm. The guidance is structured but relies heavily on illustrative examples rather than precise, executable instructions.	2 / 3
Workflow Clarity	The 5-step analysis process is clearly sequenced and the implementation checklist provides a good summary. However, there are no validation checkpoints — no step says 'verify the user has provided their resume/experience before calculating match score' or handles cases where input is incomplete. The workflow assumes all information is available.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. The massive example output (~150 lines) should be in a separate template file. The requirement classification guide, red flag lists, and edge cases could all be split into referenced documents. Everything is inlined, making this extremely long for a SKILL.md.	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: 12 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.