CtrlK
BlogDocsLog inGet started
Tessl Logo

tailored-resume-generator

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

69

1.05x
Quality

55%

Does it follow best practices?

Impact

96%

1.05x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/tailored-resume-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a genuinely actionable, well-sequenced tailoring workflow with a strong worked example, but it is padded with substantial generic resume-writing knowledge Claude already possesses and is a monolithic document with no progressive disclosure. Trimming known-knowledge sections and moving the example and special-cases content into reference files would improve both conciseness and structure.

Suggestions

Cut or drastically compress Sections 9 (Best Practices Do/Don't) and 10 (Special Considerations) to a few non-obvious points — standard resume conventions (action verbs, no photos, reverse chronological, GPA thresholds) are knowledge Claude already has.

Move the full worked example into a separate EXAMPLES.md and the role-specific guidance into a reference file, keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

Convert implicit quality checks into explicit validation checkpoints in the workflow (e.g., a step that verifies every listed skill is substantiated by an experience bullet and that no fabricated content was introduced before presenting the resume).

DimensionReasoningScore

Conciseness

At ~340 lines, the body spends large sections explaining resume-writing knowledge Claude already has: Section 9's Do/Don't list (action verbs, no first-person pronouns, no photos, reverse chronological order), Section 10's role-specific boilerplate (recent graduates list GPA if 3.5+, executives emphasize revenue growth), and generic advice like 'Proofread for grammar and consistency'. This matches 'Noticeably verbose; several unnecessary explanations or padded sections' rather than level 3's 'mostly efficient with some unnecessary explanation', because well over a third of the document is standard resume knowledge Claude needs no instruction on.

2 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: a 10-step process, an explicit bullet formula ('[Action Verb] + [What] + [How/Why] + [Result/Impact]'), specific rules ('1 page for <10 years experience, 2 pages for 10+'), ATS rules ('Include both acronyms and full terms'), and a full worked example with input and complete output. Per the scoring notes, absence of code is not penalized since guidance is actionable; minor gaps (no explicit output-quality checklist) keep it below 5.

4 / 5

Workflow Clarity

The 10 numbered steps form a coherent sequence (gather → analyze → map → structure → optimize → format → recommend → iterate) with prioritization guidance (Priority 1/2/3) and iteration/refinement built into step 8. Checkpoints are present but somewhat implicit — 'Be truthful and accurate - never fabricate' and 'Proofread for grammar and consistency' are checklist items rather than explicit validation gates — which fits 'Clear sequence with most checkpoints present; minor validation gaps' and keeps it below the level-5 feedback-loop anchor. No destructive or batch operations, so no cap applies.

4 / 5

Progressive Disclosure

The skill has no bundle files and the body is a single monolithic 340-line document with no external references at all. Section headers are well organized, but substantial content that belongs in separate files is inlined — the full example output (~45 lines), the role-specific 'Special Considerations' matrix, and the best-practice lists would all be natural separate reference files. This matches 'Some structure but could be better organized; ... content that should be separate is inline'; it is above level 2 ('minimal structure') because the section organization itself is genuinely good.

3 / 5

Total

13

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 states a clear, third-person 'what' with two concrete actions, but it lacks any 'when to use' trigger clause, which both caps completeness and weakens trigger-term quality. Adding an explicit 'Use when...' clause with natural user phrases (e.g., tailoring a resume or CV for a specific job posting, ATS optimization) would lift the two heaviest-weighted dimensions.

Suggestions

Append a trigger clause such as: 'Use when the user is applying for a job, wants to tailor a resume or CV for a specific job posting, or asks about ATS-friendly resume optimization.'

Include common synonyms users actually say — 'CV', 'customize my resume', 'ATS', 'job application' — to broaden natural keyword coverage.

Mention distinctive capabilities the body delivers (ATS keyword optimization, multiple format versions for different roles) to sharpen both specificity and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — 'Analyzes job descriptions and generates tailored resumes' — but coverage is not comprehensive; it omits capabilities the body actually delivers such as ATS keyword optimization and multiple format options. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' better than the level-4 anchor ('several specific actions; minor gaps'), and 'maximize interview chances' is a mild over-claim rather than a concrete action.

3 / 5

Completeness

The 'what' is clear (analyze job descriptions, generate tailored resumes), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, matching the anchor 'Has a clear what but when is missing or only weakly implied' — here the 'when' is entirely absent, not even weakly implied.

3 / 5

Trigger Term Quality

Natural phrases like 'job descriptions', 'tailored resumes', and 'interview chances' are present and would be said by users, but common variations are missing: 'CV', 'customize my resume', 'apply for a job', 'ATS', and 'cover letter'. This fits the anchor 'Some relevant keywords but missing common variations or synonyms'; it is not sparse enough for 2 nor covering enough for 4.

3 / 5

Distinctiveness Conflict Risk

Resume tailoring against a specific job posting is a fairly clear niche ('tailored resumes', 'job descriptions') with mostly distinct triggers; minor overlap risk remains with adjacent skills like general cover-letter writing, career coaching, or generic document editing. Not the level-5 'clear niche with distinct triggers' because 'analyze job descriptions' could plausibly fire for job-analysis or interview-prep skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.