CtrlK
BlogDocsLog inGet started
Tessl Logo

resume-formatter

Ensure ATS-friendly formatting and create clean scannable layouts

35

Quality

30%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/resume-formatter/SKILL.md
SKILL.md
Quality
Evals
Security

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 hints at a resume/document formatting skill but is too vague to be effective for skill selection. It lacks a 'Use when...' clause, misses critical trigger terms like 'resume' and 'CV', and doesn't enumerate specific concrete actions beyond generic formatting language.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to format, review, or optimize a resume or CV for applicant tracking systems.'

Include natural trigger terms users would say: 'resume', 'CV', 'job application', 'ATS', 'applicant tracking system', '.docx', '.pdf'.

List specific concrete actions such as 'reformat resume sections, optimize keyword placement, standardize heading hierarchy, remove incompatible formatting elements'.

DimensionReasoningScore

Specificity

Names a domain (ATS-friendly formatting) and two actions (ensure formatting, create layouts), but lacks specifics about what concrete tasks are performed—e.g., does it rewrite resumes, reformat documents, optimize keywords?

2 / 3

Completeness

Provides a partial 'what' but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 2, and the 'what' is also weak, so this scores a 1.

1 / 3

Trigger Term Quality

Includes 'ATS-friendly' and 'scannable layouts' which are somewhat relevant, but misses common user terms like 'resume', 'CV', 'job application', 'applicant tracking system', or file formats.

2 / 3

Distinctiveness Conflict Risk

'ATS-friendly' provides some niche specificity, but without mentioning 'resume' or 'CV' explicitly, it could overlap with general document formatting or layout 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 a comprehensive resume formatting reference but suffers from extreme verbosity, explaining many concepts Claude already knows (ATS basics, font choices, white space principles, common mistakes). It reads more like a human-facing guide than a skill for Claude. The content would benefit greatly from aggressive condensation to essential rules and templates, with better workflow sequencing for the actual formatting process.

Suggestions

Reduce content by 60-70%: Remove explanations of concepts Claude already knows (what ATS is, why formatting matters, common mistakes) and keep only the specific rules, templates, and output format.

Add a clear sequential workflow: Define explicit steps like '1. Assess current format against checklist → 2. Identify ATS compatibility issues → 3. Apply formatting fixes → 4. Generate before/after comparison → 5. Validate against checklist'.

Split detailed reference content (font specs, section formatting examples, file format guidelines) into separate referenced files to improve progressive disclosure.

Remove the 'When to Use This Skill' trigger phrases section—this is frontmatter-level metadata, not actionable skill content.

DimensionReasoningScore

Conciseness

Extremely verbose at ~300+ lines. Explains basic concepts Claude already knows (what ATS is, what fonts are safe, what white space is, common formatting mistakes). The 'Dual Audience Challenge' section, font selection lists, and 'Common Formatting Mistakes' section all explain things Claude inherently understands. Much of this could be condensed to a fraction of its size.

1 / 3

Actionability

Provides concrete formatting templates and examples (contact info layouts, experience section formats, output template), but lacks executable code or commands. The guidance is specific enough to follow but is more of a reference document than actionable instructions—it describes formatting rules rather than providing step-by-step procedures for transforming a resume.

2 / 3

Workflow Clarity

The output format section provides a structured review template, and the checklist at the end gives a validation step. However, there's no clear sequential workflow for how to actually process a resume from input to output—steps like 'assess current format → identify issues → apply fixes → validate' are not explicitly sequenced with checkpoints.

2 / 3

Progressive Disclosure

Monolithic wall of text with no references to external files. All content is inline in a single massive document. Content like detailed font specifications, common mistakes, and file format guidelines could easily be split into referenced files, but instead everything is crammed into one file with no navigation structure.

1 / 3

Total

6

/

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.