CtrlK
BlogDocsLog inGet started
Tessl Logo

job-description-analyzer

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

35

Quality

30%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/job-description-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

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 far too verbose, embedding extensive general career advice and a massive example output inline rather than focusing on concise, actionable instructions for Claude. The core analysis framework (5-step process, match calculation, requirement classification) is sound but buried under unnecessary explanation. The skill would benefit enormously from being split into a concise SKILL.md with references to supporting template and reference files.

Suggestions

Reduce the skill to ~80-100 lines by removing general career advice Claude already knows (e.g., what red flag phrases mean, basic job search strategy) and moving the example output to a separate TEMPLATE.md file.

Extract the red flags list, requirement classification guide, and edge cases into separate reference files, linked from the main SKILL.md with clear one-level-deep navigation.

Add validation checkpoints: e.g., 'Confirm user has provided their resume/experience before calculating match score' and 'Verify all required skills are accounted for before generating final score.'

Make the match calculation more actionable by providing a structured schema or algorithm rather than a single arithmetic example — e.g., define the weighting system as a reusable formula with clear input/output expectations.

DimensionReasoningScore

Conciseness

Extremely verbose at ~350+ lines. Explains obvious concepts like what 'fast-paced environment' means, includes lengthy example output that could be a template reference, explains basic job search strategy Claude already knows, and provides extensive cover letter writing advice that is general knowledge rather than skill-specific instruction.

1 / 3

Actionability

Provides a structured process with clear categories and a match calculation formula, but contains no executable code or tool commands. The match calculation is pseudocode-level arithmetic rather than an implementable algorithm. The output format example is detailed but is a static example rather than a parameterized template Claude can directly execute.

2 / 3

Workflow Clarity

The 5-step analysis process and implementation checklist provide a clear sequence, but there are no validation checkpoints or feedback loops. There's no guidance on what to do if the user's resume is incomplete, if requirements are ambiguous, or how to verify the match score calculation is reasonable before presenting it.

2 / 3

Progressive Disclosure

Monolithic wall of text with everything inline — the massive example output (~150 lines), requirement classification guide, edge cases, and cover letter templates are all in one file with no references to supporting files. The example output alone could be a separate template file, and the red flags list, classification guide, and edge cases could each be separate references.

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 names a reasonable set of actions related to job application analysis but lacks a 'Use when...' clause, which is a critical omission for skill selection. It also misses common user-facing trigger terms like 'resume', 'job search', and 'qualifications' that would help Claude match this skill to user requests. Adding explicit trigger guidance and more natural keywords would significantly improve its effectiveness.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about job applications, job fit, resume-to-job matching, or career strategy.'

Include natural trigger terms users would say, such as 'resume', 'job search', 'job application', 'qualifications', 'career', 'job fit', 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 strategies.'

DimensionReasoningScore

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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
paramchoudhary/resumeskills
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.