interview-prep-generator

Generate STAR stories, practice questions, and talking points from resume

Quality

38%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/interview-prep-generator/SKILL.md

Quality

Discovery

50%

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 names specific, concrete deliverables (STAR stories, practice questions, talking points) and occupies a distinct niche around interview preparation from a resume. However, it lacks a 'Use when...' clause and misses important trigger terms like 'interview prep', 'behavioral questions', or 'job interview' that users would naturally use when seeking this skill.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for interview preparation, behavioral question practice, or help turning their resume into interview-ready content.'

Include additional natural trigger terms users would say, such as 'interview prep', 'behavioral questions', 'job interview', 'mock interview', and 'CV'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generate STAR stories', 'practice questions', and 'talking points from resume'. These are clear, actionable outputs.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is only weakly implied, this scores a 1.	1 / 3
Trigger Term Quality	Includes some natural keywords like 'STAR stories', 'practice questions', 'talking points', and 'resume', but misses common variations users might say such as 'interview prep', 'behavioral questions', 'job interview', 'mock interview', or 'CV'.	2 / 3
Distinctiveness Conflict Risk	The combination of STAR stories, interview practice questions, and resume-based talking points creates a clear niche around interview preparation that is unlikely to conflict with other skills.	3 / 3
	Total	9 / 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 but excessively verbose interview preparation guide that reads more like a career coaching handbook than a concise skill instruction for Claude. It contains substantial amounts of general knowledge Claude already possesses (common interview questions, basic STAR methodology, interview etiquette) and would benefit enormously from being trimmed to its unique value: the output format template, the story banking process tied to resume bullets, and the role analysis framework. The lack of any bundle files despite the massive content length is a significant structural weakness.

Suggestions

Reduce content by 60-70%: Remove common interview questions lists, generic advice (salary deflection, weakness answers), and STAR method explanation — Claude already knows these. Focus on the output format template and the resume-to-STAR conversion process.

Split into bundle files: Move question banks to QUESTIONS.md, STAR examples to EXAMPLES.md, and difficult question handling to DIFFICULT_QUESTIONS.md, keeping SKILL.md as a concise overview with references.

Add explicit workflow for Claude: Define clear decision points like 'If user provides job description → do X; if only resume → do Y; if both → do Z' rather than generic phases.

Add validation steps: Include checkpoints like 'Verify each STAR story has quantified results' and 'Confirm stories cover at least 3 of the 5 competency categories' to ensure output quality.

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 generic career coaching content rather than actionable skill instructions.	1 / 3
Actionability	Provides templates and examples (STAR story template, output format) which are somewhat actionable, but the skill is fundamentally about generating text content rather than executing code. The output format template is useful, but much of the content is descriptive lists (common questions, questions to ask) rather than concrete instructions for how Claude should process a resume or job description to generate prep materials.	2 / 3
Workflow Clarity	There's a phased framework (Role Analysis → Story Banking → Mock Preparation) and an implementation checklist, but the actual workflow for Claude to follow when a user requests interview prep is unclear. Steps like 'Research company interview style' and 'Practice out loud' are not things Claude can do. The output format section provides structure but lacks explicit validation steps or decision points for handling incomplete inputs (e.g., no job description provided).	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline despite being far too long for a single SKILL.md. The extensive question lists, role-specific sections, and detailed examples for handling difficult questions could easily be split into separate reference files (e.g., STAR_EXAMPLES.md, COMMON_QUESTIONS.md, DIFFICULT_QUESTIONS.md).	1 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

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: 12 days ago

Table of Contents

Discovery Implementation Validation

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.