creative-portfolio-resume
Balance visual design with ATS compatibility for creative roles
32
24%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/creative-portfolio-resume/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too abstract and goal-oriented rather than action-oriented. It fails to specify concrete actions the skill performs, omits an explicit 'Use when...' clause, and lacks key trigger terms like 'resume' or 'CV' that would help Claude correctly select this skill. The concept of balancing visual design with ATS compatibility for creative roles is a valid niche, but the description needs significantly more detail.
Suggestions
Add specific concrete actions such as 'Formats resumes with visual design elements (color, layout, icons) while maintaining ATS-parseable structure for creative roles like graphic design, UX, and marketing.'
Include a 'Use when...' clause with trigger terms like 'creative resume', 'designer CV', 'ATS-friendly portfolio resume', 'visual resume', or 'creative role application'.
Add key natural-language trigger terms users would say: 'resume', 'CV', 'applicant tracking system', 'creative job', 'design portfolio resume', '.docx', '.pdf'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is vague — 'balance visual design with ATS compatibility' doesn't list any concrete actions (e.g., format sections, add color accents, structure keywords). It describes a general goal rather than specific capabilities. | 1 / 3 |
Completeness | The 'what' is only vaguely implied (balancing design and ATS compatibility) and there is no explicit 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 2, but the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant terms like 'ATS', 'visual design', and 'creative roles' that users might mention, but misses common variations like 'resume', 'CV', 'applicant tracking system', 'portfolio', 'graphic design resume', or file formats. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'creative roles' and 'ATS compatibility' together provides some niche specificity, but without mentioning 'resume' or 'CV' explicitly, it could overlap with general design or ATS-related skills. | 2 / 3 |
Total | 6 / 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 excessively verbose, spending most of its token budget on general creative career advice and design principles that Claude already knows. While it provides some useful structure (two-version approach, field-specific sections, checklists), it lacks concrete actionable steps, validation checkpoints, and proper content organization. The skill reads more like a blog post about creative resumes than a focused instruction set for Claude.
Suggestions
Cut content by 60-70%: remove explanations of basic design principles, tool recommendations, and general career advice that Claude already knows. Focus on the specific decision framework (ATS vs designed) and the output template.
Add a concrete step-by-step workflow with validation: e.g., 1) Determine version needed, 2) Generate content, 3) Verify ATS compatibility by checking for forbidden elements, 4) Validate portfolio links exist.
Split field-specific guidance and design checklists into separate referenced files to improve progressive disclosure and reduce the main skill's token footprint.
Make the output format more actionable by providing a complete filled-in example rather than just a template with placeholder brackets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~250+ lines. Explains obvious concepts Claude already knows (what ATS is, that 'your resume IS a design sample', basic design principles like 'clarity over cleverness'). Lists of tools, field-specific guidance, and multiple checklists are padded with information that doesn't add actionable value. Much of this is general career advice rather than specific instructions. | 1 / 3 |
Actionability | Provides some concrete guidance through checklists, safe/unsafe design elements, and an output format template. However, there's no executable code, no actual resume templates or markup, and much of the content is advisory rather than instructional. The output format is a markdown template but not truly executable or copy-paste ready for generating an actual resume. | 2 / 3 |
Workflow Clarity | The two-version strategy provides a clear high-level workflow, and the decision tree for when to use each version is helpful. However, there's no sequenced step-by-step process for actually creating either version, no validation checkpoints (e.g., testing ATS parsing), and no feedback loops for verifying the output works as intended. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files despite having extensive sections (field-specific guidance, design execution tips, tools) that could be split out. Everything is inline in one massive document with no bundle files to support it. The content would benefit greatly from splitting into separate reference files. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- paramchoudhary/resumeskills
- Commit
24c6edc
- 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.