resume-bullet-writer
Transform weak resume bullets into achievement-focused statements with metrics and impact
37
33%
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-bullet-writer/SKILL.mdQuality
Discovery
40%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 a clear niche—resume bullet improvement—with reasonable specificity about the transformation approach (achievement-focused, metrics, impact). However, it lacks an explicit 'Use when...' clause, which hurts completeness, and could benefit from broader trigger term coverage including synonyms like 'CV', 'work experience', or 'quantify'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to improve, rewrite, or strengthen resume bullets, CV entries, or work experience descriptions.'
Include additional natural trigger terms users might say, such as 'CV', 'work experience', 'bullet points', 'quantify accomplishments', 'job application'.
List additional concrete actions beyond 'transform', such as 'adds quantifiable metrics, highlights outcomes, and restructures vague descriptions into results-driven statements'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (resume bullets) and a core action (transform into achievement-focused statements), and mentions metrics and impact, but doesn't list multiple distinct concrete actions beyond the single transformation. | 2 / 3 |
Completeness | Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, and per the rubric guidelines, a missing 'Use when' clause caps completeness at 2—but since the 'when' is entirely absent and only weakly implied, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes natural terms like 'resume bullets', 'achievement', 'metrics', and 'impact' which users might say, but misses common variations like 'CV', 'work experience', 'job application', 'bullet points', or 'quantify accomplishments'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on transforming resume bullets specifically into achievement-focused statements with metrics is a clear, narrow niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 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 a comprehensive resume bullet writing guide but suffers severely from verbosity—it explains many concepts Claude already knows (action verbs, STAR method, passive vs. active voice) and includes extensive industry-specific examples that could be generated on demand. The core value (X-Y-Z formula, output format, quantification strategies) is buried in a 300+ line monolith that wastes context window. The content reads more like a blog post or career coaching article than a concise skill instruction.
Suggestions
Reduce content by 70%+: Remove power verb lists, industry-specific examples, and common mistakes sections—Claude already knows these. Keep only the X-Y-Z formula, output format, quantification strategies, and the bullet writing process.
Split remaining reference material into bundle files: Move industry examples to EXAMPLES.md, power verbs to VERBS.md, and frameworks to FRAMEWORKS.md with clear one-level references from the main skill.
Add validation/feedback loop: Include criteria for evaluating whether a rewritten bullet is strong enough (e.g., 'If the bullet lacks a metric after rewriting, ask the user for specific numbers before finalizing').
Tighten the output format section: The current format is good but could include a brief example of the complete expected output for a batch of 3 bullets to make it fully copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 300+ lines. Extensively explains concepts Claude already knows (what STAR method is, what action verbs are, what passive language is). Lists of power verbs, industry examples for 7+ industries, and common mistakes are all knowledge Claude possesses. The content could be reduced by 70%+ while retaining all novel guidance. | 1 / 3 |
Actionability | Provides concrete before/after examples and clear formulas (X-Y-Z, STAR, CAR), which is useful. However, much of it is descriptive rather than instructive—it reads more like a reference article than executable guidance. The output format template and step-by-step process are actionable, but the bulk is illustrative padding. | 2 / 3 |
Workflow Clarity | The 'Bullet Writing Process' section provides a clear 5-step sequence, and the implementation checklist is useful. However, there are no validation checkpoints or feedback loops—no guidance on verifying the rewritten bullet is actually stronger, no criteria for when to ask the user for more information vs. estimate, and no error recovery steps. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—power verbs, industry examples, frameworks, special situations—is inlined despite being ideal candidates for separate reference files. The skill would benefit enormously from splitting industry examples, verb lists, and frameworks into separate 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.