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 reads more like a comprehensive academic CV writing guide than a concise skill file for Claude. It extensively explains concepts Claude already knows (what sections go in a CV, what a resume vs CV is, discipline conventions) rather than focusing on specific formatting rules, decision logic, or unique instructions. The content would benefit enormously from aggressive trimming and splitting into referenced files.
Suggestions
Reduce content by 60-70%: Remove the resume vs CV comparison table, discipline-specific conventions, CV length guidelines, and basic explanations of what each section contains—Claude already knows these things. Focus only on specific formatting rules and decision logic.
Split detailed section formatting examples into a separate SECTIONS.md reference file, keeping only a brief overview and the output template in SKILL.md.
Add a clear sequential workflow: e.g., 1) Identify position type → 2) Determine section order → 3) Gather information from user → 4) Format sections → 5) Review against checklist, with explicit decision points.
Create a separate CONVENTIONS.md for discipline-specific formatting rules and role-specific emphasis, referenced from the main skill with clear one-level-deep links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains obvious concepts like the difference between a resume and CV, what each CV section means, and discipline-specific conventions—all knowledge Claude already possesses. The comparison table, length guidelines, and most section descriptions are unnecessary padding. | 1 / 3 |
Actionability | Provides concrete formatting examples for each section which are useful templates, but these are static text examples rather than executable code/commands. The guidance is more of a reference document than actionable instructions for generating a specific output. The output format template at the end adds some actionability. | 2 / 3 |
Workflow Clarity | The 'When to Use' section and output format provide some workflow structure, and the checklist at the end serves as a validation step. However, there's no clear sequential process for gathering information, making decisions about section ordering, or iterating with the user. The process of actually building the CV is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—section guides, discipline conventions, role-specific emphasis, formatting examples—is inlined into a single massive document. Much of this content (e.g., discipline-specific conventions, role-specific emphasis) could be split into referenced files. | 1 / 3 |
Total | 6 / 12 Passed |