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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/resume-formatter/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 excessively verbose, spending many tokens explaining concepts Claude already understands (ATS basics, font choices, white space principles, common mistakes). While it provides useful formatting templates and concrete examples, the lack of a clear processing workflow and the monolithic structure significantly reduce its effectiveness. The content would benefit greatly from aggressive trimming and restructuring into a concise overview with referenced detail files.

Suggestions

Cut content by 60-70%: Remove explanations of basic concepts (what ATS is, what white space is, common mistakes) and focus only on the specific formatting rules and templates Claude should apply.

Add a clear step-by-step workflow: Define a sequenced process like 1) Assess current format, 2) Identify ATS issues, 3) Apply formatting template, 4) Verify against checklist, with explicit validation at each step.

Split into multiple files: Move detailed specs (font sizes, margin rules, section templates) into referenced files like FORMATTING_SPECS.md and ATS_RULES.md, keeping SKILL.md as a concise overview.

Remove the 'Common Formatting Mistakes' and 'Visual Hierarchy Principles' sections entirely—Claude already knows these concepts and they add no actionable value.

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, visual hierarchy principles, and white space management sections are all unnecessary padding. Much of this could be condensed to a fraction of the size.

1 / 3

Actionability

Provides concrete formatting templates and examples (contact info layouts, experience section formats, output template), which is useful. However, since this is a formatting skill, there's no executable code or tool-based workflow—it's mostly declarative guidelines and checklists rather than precise instructions Claude can directly execute on a given resume.

2 / 3

Workflow Clarity

The output format section provides a structured review template, and the checklist at the end is helpful. However, there's no clear step-by-step workflow for how to actually process and reformat a resume—no validation steps, no feedback loops, no sequenced process for applying changes and verifying results.

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 the full list of formatting mistakes, detailed font/margin specs, and file format guidelines could easily be split into referenced files. No bundle files exist to support progressive disclosure.

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 hints at a resume/CV formatting skill but fails to explicitly mention resumes, CVs, or job applications, which are the most natural trigger terms users would use. It lacks a 'Use when...' clause entirely and doesn't list enough concrete actions to clearly communicate the skill's capabilities. The description needs significant improvement in completeness and trigger term coverage.

Suggestions

Add explicit mention of 'resume', 'CV', 'job application' as these are the primary terms users would naturally use when needing this skill.

Add a 'Use when...' clause such as 'Use when the user asks about resume formatting, CV creation, job application documents, or ATS optimization.'

List more specific actions like 'restructure resume sections, optimize keywords for applicant tracking systems, format bullet points, standardize headings and dates.'

DimensionReasoningScore

Specificity

Names a domain (ATS-friendly formatting) and two actions (ensure formatting, create layouts), but lacks specific concrete actions like 'rewrite bullet points', 'optimize keyword placement', or 'restructure sections'.

2 / 3

Completeness

Provides a partial 'what' but completely lacks a 'when' clause or any explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, warranting 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' is a somewhat distinctive term pointing to resume/CV formatting, but without mentioning 'resume' or 'CV' explicitly, it could overlap with general document formatting or layout 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.