CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

residency-interview-prep

Mock interview preparation tool for residency Match interviews. Generates.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/residency-interview-prep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body contains a real, usable core (question types, parameters, output schema, runnable script) buried in a large amount of generic template boilerplate, including circular cross-references and an off-topic 'academic writing' trigger bullet. Executable guidance is present but partially incorrect (--help is unimplemented, the experience parameter is unsupported), and the actual mock-interview workflow is never described.

Suggestions

Remove the circular placeholder sections ('See `## Features` above', 'See `## Prerequisites` above', 'See `## Workflow` above') and the off-topic 'academic writing tasks' trigger bullet; keep only sections that carry task-specific content.

Fix the executable guidance: drop or implement '--help', align the documented parameters with what scripts/main.py actually accepts (question_type and specialty are supported, experience is not), and document the real CLI ('python scripts/main.py <behavioral|clinical|program|ethical>').

Describe the actual mock-interview workflow (generate question → capture the user's answer → give STAR-based feedback on key_points/pitfalls) as a single sequenced list, and replace the generic 'Reference material available in references/' with a pointed reference to guidelines.md stating when to use it.

DimensionReasoningScore

Conciseness

The body is padded with template boilerplate: circular self-references ('See `## Features` above for related details', 'See `## Prerequisites` above'), an off-topic 'When to Use' bullet about 'academic writing tasks' seemingly copied from another skill, and generic Risk Assessment / Security Checklist / Lifecycle / Evaluation sections that add no task-specific value. It is not a 1 because genuine task content (features, parameter table, output format) is interleaved and no space is spent explaining concepts Claude already knows.

2 / 5

Actionability

Concrete commands exist ('python -m py_compile scripts/main.py', 'python scripts/main.py demo') alongside a parameter table and JSON output format, but 'python scripts/main.py --help' is not implemented (argv[1] is treated as a question type and silently falls back to behavioral), and the documented 'experience' parameter is not accepted by the script. These are more than minor gaps, so it sits at anchor 3 rather than 4.

3 / 5

Workflow Clarity

Steps are listed with a compile checkpoint, error handling, and a fallback path, but the body contains two overlapping generic step lists ('Example run plan' and 'Workflow') that apply to any skill, while the core mock-interview interaction loop (ask question → user answers → give STAR feedback) is never laid out. Sequence present but checkpoints are generic and duplicated, matching anchor 3.

3 / 5

Progressive Disclosure

Referenced paths are real and one level deep ('scripts/main.py', 'references/guidelines.md' both exist), but the body only gestures at them generically ('Reference material available in `references/`') without signaling what each contains or when to consult it, and ~190 lines of inline template boilerplate dilute the overview. Structure exists but organization and reference signaling are imperfect, matching anchor 3.

3 / 5

Total

11

/

20

Passed

Description

48%Weight 40%Scale 1-5

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 distinct, well-chosen niche but is functionally incomplete: the sentence is truncated at 'Generates.', leaving the core capability unstated, and no 'when to use' trigger guidance is provided. It reads as a template placeholder rather than a finished description.

Suggestions

Complete the truncated sentence with concrete actions, e.g. 'Generates behavioral, clinical, program, and ethical residency interview questions with STAR-based answer guidance and common pitfalls.'

Add an explicit trigger clause, e.g. 'Use when preparing for residency or NRMP Match interviews, practicing interview questions, or getting feedback on answers.'

Include natural synonyms users would say — 'residency interview', 'interview practice', 'interview prep', 'STAR format' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('mock interview preparation', 'residency Match interviews') but its only action verb is truncated: 'Generates.' with no object, so it never states what is generated. This matches anchor 2 ('names the domain but actions are minimal or generic') rather than 3, which requires one or two completed concrete actions like 'Generates behavioral and clinical interview questions'.

2 / 5

Completeness

A partial 'what' is present (a mock interview preparation tool for residency Match interviews) but it is cut off mid-sentence, and there is no 'Use when…' clause or equivalent trigger guidance anywhere. Per the judging guidelines a missing 'Use when…' clause caps completeness at 3; it cannot be 4 because the 'when' is entirely absent rather than merely imprecise, and it is above 2 because the 'what' is clearly stated at the domain level.

3 / 5

Trigger Term Quality

'Mock interview' and 'residency Match' are phrases a user would naturally say, giving some relevant keywords, but common variations and synonyms are missing: 'residency interview', 'interview practice', 'interview prep', 'STAR answers', 'Match preparation'. Anchor 3 ('some relevant keywords but missing common variations') fits better than 4, whose keyword coverage is described as good.

3 / 5

Distinctiveness Conflict Risk

'Residency Match interviews' carves out a clear niche distinct from generic job-interview or academic skills, leaving only minor overlap risk with closely related interview-prep skills — anchor 4. It does not reach anchor 5 because that anchor's example includes explicit distinct trigger phrases ('Use when…'), which this description lacks.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/residency-interview-prep/SKILL.md

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.