CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview-prep

Mock interview coach for AI engineering roles, built on the interview bank of AI Engineering from Scratch. Asks one question or one incident scenario, stops, and waits for the learner's own answer. Then it grades the answer against the bank, asks follow-ups one at a time, sends each gap to the lessons and manual sections that teach it, and keeps an append-only record in INTERVIEW-LEARNING.md. Trigger phrases: "interview prep", "mock interview", "ask me an interview question", "practise for my AI engineering interview", "run an incident scenario", "debugging round", "system design round", "inference engineer loop", "review my interview gaps", "how ready am I for the interview"

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is interview-prep in rohitg00/ai-engineering-from-scratch

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

Excellent instruction-only skill content: concrete, executable guidance throughout, tightly sequenced workflows with per-step validation checkpoints, and a clean one-level-deep reference structure. The only improvement opportunity is consolidating the triple restatement of the answer-hiding rule across the core rule, Never list, and Good/bad turns sections.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no explanations of concepts Claude already knows, and dense tables instead of prose. It falls to 4 rather than 5 because the don't-reveal-answer rule is restated three times ("The core rule", the "Never list", and the "Good and bad turns" table), which could be trimmed. It is above anchor 3 since there is no padded or unnecessary explanation.

4 / 5

Actionability

Guidance is fully concrete and executable for an instruction-only skill: exact repo paths (interviews/questions/<card-id>/<id>.md), the raw.githubusercontent URL fallback, exact bank section names to show or keep private, a host-invocation table with literal forms, row formats for the state file, and near-verbatim example utterances ("Partial. You named <a claim>. Missing: <the main claim, in your words>."), covering the common cases.

5 / 5

Workflow Clarity

Question mode is a clearly sequenced 8-step process with an explicit "Done when" validation checkpoint after each step; mode selection has precedence rules; and state-file writes are guarded by an explicit validation loop (step 8 checks the rows were appended, and "Never edit or delete a row" enforces append-only behavior). This matches anchor 5's explicit validation steps and feedback loops.

5 / 5

Progressive Disclosure

The body is a clear overview that splits detail into six reference files, each existing in references/ and well-signaled by a References table with a "Read it when" column plus inline links at point of use. References are one level deep (grading.md, routing.md, etc. only cross-link siblings, not chained content), and inlined material (mode table, judgment buckets, good/bad turns) is core orchestration that belongs in the main file.

5 / 5

Total

19

/

20

Passed

Description

88%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.

A strong description: concrete third-person action list, explicit trigger-phrase guidance, and a well-defined niche. The only weaknesses are a few missing natural trigger variants (notably the US spelling "practice") and slightly generic round-based triggers that could overlap with non-interview practice skills.

Suggestions

Add the US spelling variant "practice for my AI engineering interview" alongside "practise", since trigger matching is literal and American users type "practice".

Consider scoping the round-based triggers ("debugging round", "system design round") with the interview context, e.g. "interview debugging round", to reduce overlap with general practice or system-design skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Asks one question or one incident scenario", "grades the answer against the bank", "asks follow-ups one at a time", "sends each gap to the lessons and manual sections that teach it", "keeps an append-only record in INTERVIEW-LEARNING.md" — with comprehensive coverage of the skill's behavior, all in third-person voice. This matches the anchor-5 example (multiple specific concrete actions) and exceeds anchor 4, which allows coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the concrete coach behavior (ask, wait, grade, follow up, route gaps, record), and the "when" is an explicit "Trigger phrases:" list with concrete phrases — mirroring the anchor-5 example structure. Anchor 4 would require the "when" to be less explicit, which is not the case.

5 / 5

Trigger Term Quality

Ten natural quoted trigger phrases ("interview prep", "mock interview", "ask me an interview question", "run an incident scenario", "debugging round", "review my interview gaps", "how ready am I for the interview") give good keyword coverage. It falls short of anchor 5 because a few natural variants are missing: the US spelling "practice" (only "practise" appears), plus common phrasings like "technical interview" or "behavioral round".

4 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (mock interviews for AI engineering roles, tied to a specific interview bank), but triggers like "system design round" and "debugging round" are phrases a user could also say when seeking general practice rather than interview coaching — minor overlap risk with closely related skills, matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

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

rohitg00/ai-engineering-from-scratch

Path

.claude/skills/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.