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 most of its token budget on generic creative industry advice and design principles that Claude already knows. While it provides some useful structure (two-version strategy, checklists, output template), it lacks concrete executable guidance and validation steps. The content would benefit enormously from being cut by 60-70% and split into referenced sub-files for field-specific guidance.
Suggestions
Cut the content by at least 60%: remove generic design advice (typography basics, color theory), tool recommendations, and obvious field-specific guidance (writers should write well) that Claude already knows.
Add concrete validation steps: include how to test ATS parsing (e.g., specific online tools or copy-paste test), and a feedback loop for verifying the designed version prints correctly in B&W.
Split field-specific guidance into a separate reference file (e.g., CREATIVE-FIELDS.md) and tool recommendations into another, keeping SKILL.md as a lean overview with clear cross-references.
Replace the advisory content with concrete, executable examples: provide an actual ATS-safe resume snippet in markdown/HTML and a specific designed version example, rather than abstract principles.
| 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, generic design advice, and field-specific guidance that amounts to common sense (writers should have 'zero errors', photographers should 'let portfolio speak') all waste tokens. | 1 / 3 |
Actionability | Provides some concrete guidance like the ATS-safe vs. avoid checklists and the output format template. However, most content is advisory rather than executable—no actual code, no specific font names for ATS-safe fonts, no concrete resume templates or markup. The output format is a markdown template but is more of a planning document than an executable artifact. | 2 / 3 |
Workflow Clarity | The two-version strategy provides a clear high-level workflow, and the 'when to use each version' section is well-organized. However, there's no step-by-step process for actually creating either version, no validation steps (e.g., testing ATS parsing), and no feedback loops for verifying the designed version meets accessibility or print requirements. | 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 easily be split out. No bundle files exist, and no attempt is made to organize content across multiple files. Everything is inline in one massive document. | 1 / 3 |
Total | 6 / 12 Passed |