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 interview preparation guide for humans than a concise, actionable skill for Claude. It is extremely verbose, explaining many concepts Claude already knows (STAR method, common interview questions, basic etiquette), and inlines hundreds of lines of reference material that should either be in separate files or omitted entirely. The output format template is the strongest element, but the skill would benefit enormously from being reduced to ~50-80 lines focusing on the transformation process from resume → prep materials.
Suggestions
Cut content by 70-80%: Remove common interview questions lists, basic STAR method explanation, salary negotiation advice, and interview etiquette tips that Claude already knows. Focus only on the transformation process from resume/JD inputs to structured output.
Extract reference material into bundle files: Move question banks, example STAR stories, and 'questions to ask' lists into separate .md files referenced from the main skill, keeping SKILL.md as a concise overview with the output template and core workflow.
Add explicit validation steps to the workflow: Include checkpoints like 'verify each competency from the JD is covered by at least one STAR story' and 'confirm metrics/quantified results appear in every Result section'.
Make the core workflow more concrete: Instead of describing phases abstractly, provide a clear numbered sequence of what Claude should do when given a resume and job description (e.g., 'Step 1: Extract top 5 competencies from JD. Step 2: For each resume bullet, generate a STAR expansion. Step 3: Map stories to competencies, identify gaps.').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains concepts Claude already knows well (what STAR stands for, how to answer 'greatest weakness', basic interview etiquette like 'don't criticize past employers'). Lists of common interview questions and 'questions to avoid asking' are general knowledge that don't earn their token cost. Much of this is a generic interview guide, not a skill teaching Claude something new. | 1 / 3 |
Actionability | The output format template and STAR story template are concrete and usable. However, most content is descriptive lists (question banks, competency lists) rather than executable instructions. There's no code or tool usage, and the 'process' is more of a framework description than step-by-step executable guidance for Claude to follow when given a resume and job description. | 2 / 3 |
Workflow Clarity | There is a phased framework (Role Analysis → Story Banking → Mock Preparation) and an implementation checklist, but the steps lack validation checkpoints. For example, there's no guidance on verifying story quality, checking coverage of competencies, or iterating based on gaps. The phases are described but not tightly sequenced with clear decision points. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—question banks, example stories, salary negotiation tips, company research notes—is inlined in a single massive document. Much of this (e.g., common interview questions by category, questions to ask interviewers) could be split into separate reference files, with the SKILL.md serving as a concise overview. | 1 / 3 |
Total | 6 / 12 Passed |