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 a comprehensive but excessively verbose guide that reads more like a career advice blog post than a concise skill instruction. Its main strengths are the concrete before/after bullet examples and the structured output format template. However, it significantly over-explains concepts Claude already knows, lacks a clear step-by-step transformation workflow, and dumps all content into a single monolithic file without any progressive disclosure.
Suggestions
Reduce content by 60-70%: Remove obvious advice (don't include photos, Microsoft Office is assumed), category listings Claude already knows (common frameworks, databases), and interview prep tips that are outside the skill's scope.
Add a clear numbered workflow: e.g., 1) Identify target role type, 2) Extract current skills and map to categories, 3) Transform each bullet using the formula, 4) Verify each bullet has metrics, 5) Generate output in template format.
Split role-specific examples (SWE, Data Engineer, DevOps, PM) into a separate EXAMPLES.md file and reference it, keeping only one representative example inline.
Add a validation step: after generating optimized bullets, verify each contains [Action Verb + Technical What + Scale/Impact + Technology] and flag any that are missing components.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains obvious concepts like what to include in contact info, what GitHub READMEs should contain, and lists every possible database/framework category. Much of this is general knowledge Claude already possesses (e.g., 'Don't include: Photo', 'Microsoft Office is assumed'). The skill reads more like a blog post than a concise instruction set. | 1 / 3 |
Actionability | Provides concrete examples of good vs bad bullets and a clear output format template, which is useful. However, much of the content is descriptive guidance rather than executable instructions—it lists categories and tips rather than giving Claude a precise algorithm to follow when transforming a resume. The output format section is the most actionable part. | 2 / 3 |
Workflow Clarity | The output format section at the end provides a reasonable workflow structure (restructure skills → improve bullets → suggest projects → GitHub recommendations → gaps). However, there's no explicit step-by-step process for how to analyze and transform a resume, no validation checkpoints, and no feedback loop for verifying improvements against the job description. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Everything is inlined—role-specific examples, GitHub tips, education formatting, ATS guidance—all in one massive document. Content like role-specific bullet examples, project formatting guides, and GitHub optimization tips could easily be split into separate referenced files. | 1 / 3 |
Total | 6 / 12 Passed |