resume-section-builder
Create targeted resume sections optimized for different experience levels and roles
35
30%
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/resume-section-builder/SKILL.mdQuality
Discovery
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 identifies the domain (resume creation) and hints at customization by experience level and role, but lacks concrete action details and has no explicit trigger guidance ('Use when...'). It would benefit from listing specific actions and including natural user trigger terms to help Claude reliably select this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'resume', 'CV', 'job application', 'work history', 'career summary'.
List specific concrete actions such as 'generate professional summaries, write achievement-based bullet points, tailor skills sections to job descriptions'.
Include common keyword variations users might use: 'CV', 'curriculum vitae', 'job application', 'career profile', 'work experience section'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (resume sections) and mentions optimization for experience levels and roles, but doesn't list specific concrete actions like 'write bullet points, tailor skills sections, generate summaries'. | 2 / 3 |
Completeness | It describes what the skill does (create resume sections) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also somewhat vague, this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes 'resume' and 'experience levels' and 'roles' which are relevant keywords, but misses common variations users might say like 'CV', 'job application', 'work experience', 'career summary', or 'cover letter'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on resume sections is somewhat specific and distinguishable from generic writing skills, but could overlap with general writing, career coaching, or document formatting skills without clearer trigger terms. | 2 / 3 |
Total | 7 / 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 reads like a comprehensive resume-writing guide rather than a targeted skill for Claude. It is excessively verbose, explaining concepts Claude already understands (resume conventions, what to include/exclude in standard sections), and packs everything into a single monolithic file. While the examples and templates provide some actionable value, the lack of workflow structure, validation steps, and progressive disclosure significantly reduce its effectiveness as a skill file.
Suggestions
Reduce content by 60-70%: Remove general resume knowledge Claude already has (e.g., 'don't write in third person', 'skip Microsoft Office') and focus only on the specific framework/formula and output format.
Split into multiple files: Move career-stage-specific examples into separate reference files (e.g., ENTRY_LEVEL.md, SENIOR.md, CAREER_CHANGER.md) and keep SKILL.md as a concise overview with navigation links.
Add a clear workflow with validation: Define a step-by-step process like 'gather user context → determine career stage → select section order → draft sections → validate against checklist → present output' with explicit checkpoints.
Tighten the output format template: Make it more prescriptive about what Claude should actually produce, rather than a loose markdown suggestion that mirrors the entire skill's content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 300+ lines. Much of this is general resume-writing knowledge that Claude already knows (what to include in education sections, what soft skills are, that Microsoft Office is assumed). The extensive examples for every career stage and situation inflate token usage significantly without adding novel insight. | 1 / 3 |
Actionability | Provides concrete examples and templates for each section type, which is useful. However, the content is more of a reference guide than executable instructions—there are no specific commands or tools to run, and the output format template is a suggestion rather than a precise specification. The examples are illustrative but not truly 'copy-paste ready' since they require heavy customization. | 2 / 3 |
Workflow Clarity | The skill provides section ordering recommendations and a final checklist, which gives some workflow structure. However, there's no clear step-by-step process for building sections (e.g., gather info → draft → validate → refine), no validation checkpoints during the process, and no feedback loops for iterating on section quality. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—summaries, skills, experience, education, additional sections, ordering, output format, and checklists—is crammed into a single file. Much of this could be split into separate reference files (e.g., examples by career stage, section format templates) with the SKILL.md serving as a concise overview. | 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.