resume-tailoring
Use when creating tailored resumes for job applications - researches company/role, creates optimized templates, conducts branching experience discovery to surface undocumented skills, and generates professional multi-format resumes from user's resume library while maintaining factual integrity
69
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/resume-tailoring/SKILL.mdQuality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates both what the skill does and when to use it, with multiple specific capabilities listed. Its main weakness is in trigger term quality—it uses some internal jargon ('branching experience discovery', 'resume library') that users wouldn't naturally say, and it misses common synonyms like 'CV' or 'apply for a job'. The explicit 'Use when' clause and distinctive feature set make it effective for skill selection.
Suggestions
Add common user-facing synonyms and variations such as 'CV', 'curriculum vitae', 'job search', 'apply for a job', or 'tailor my resume' to improve trigger term coverage.
Replace internal jargon like 'branching experience discovery' and 'resume library' with more natural language users would recognize, e.g., 'guided interview to uncover hidden skills' and 'existing resume collection'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: researches company/role, creates optimized templates, conducts branching experience discovery, surfaces undocumented skills, generates multi-format resumes from a resume library, and maintains factual integrity. | 3 / 3 |
Completeness | Clearly answers both 'what' (researches company/role, creates templates, conducts experience discovery, generates multi-format resumes) and 'when' with an explicit trigger clause ('Use when creating tailored resumes for job applications'). | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'resumes', 'job applications', 'company/role', and 'multi-format resumes', but misses common user variations like 'CV', 'cover letter', 'job search', 'apply for a job', or 'tailor my resume'. Some terms like 'branching experience discovery' and 'resume library' are internal jargon rather than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around tailored resume creation for job applications, including unique differentiators like branching experience discovery, resume library management, and company/role research that would not easily conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
39%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill demonstrates deep domain expertise and thorough workflow design with excellent checkpoint/validation patterns, but critically fails at conciseness and progressive disclosure. The ~800+ line monolithic file contains extensive content (multi-job workflows, edge cases, testing guidelines, usage examples) that should be distributed across the referenced supporting files. The result is a token-expensive skill that buries its core value in excessive detail.
Suggestions
Move the multi-job workflow details, edge cases, usage examples, and testing guidelines into separate referenced files (e.g., edge-cases.md, examples.md, testing.md) - keep only the Quick Start and phase summaries in SKILL.md
Replace pseudocode blocks with either executable code or remove them entirely - Claude can infer implementation from clear instructions without seeing Python pseudo-implementations
Reduce checkpoint dialogue templates to a single example pattern rather than repeating the full dialogue format for every phase
Trim the Phase 0 JSON schema and Phase 5 metadata JSON to brief descriptions of what to track, rather than full schema definitions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~800+ lines. Contains extensive pseudocode, JSON schemas, ASCII diagrams, and detailed edge case handling that could be split into referenced files. Much of the content (multi-job workflow, batch processing details, testing guidelines) bloats the main skill file. Repeated checkpoint dialogue templates and example conversations add significant token overhead. | 1 / 3 |
Actionability | Provides structured workflows with clear phases and checkpoint dialogues, but relies heavily on pseudocode rather than executable code. References sub-skills and external files (research-prompts.md, matching-strategies.md, branching-questions.md, multi-job-workflow.md) without providing their content. The scoring formula and matching strategies are described but not fully executable. | 2 / 3 |
Workflow Clarity | Excellent multi-phase workflow with explicit checkpoints at every phase transition requiring user confirmation before proceeding. Includes clear error recovery paths, feedback loops (revise → re-present → approve), graceful degradation strategies, and detailed edge case handling with specific options for each scenario. | 3 / 3 |
Progressive Disclosure | Despite referencing external files (research-prompts.md, matching-strategies.md, branching-questions.md, multi-job-workflow.md), the main SKILL.md is a monolithic wall of text containing enormous detail that should be in those referenced files. The multi-job workflow, all 6 edge cases, 5 usage examples, and 7 test cases are all inline rather than appropriately split into supporting documents. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1320 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- varunr89/resume-tailoring-skill
- Commit
9a4a0f2
- 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.