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

96%

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

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.

A tightly written, highly operational interviewer playbook: concrete file paths, per-step Done-when checkpoints, edge-case handling, and a clean one-level-deep reference bundle. Its only weakness is mild redundancy — the answer-concealment rule is restated across the core rule, the good/bad turns table, and the Never list.

Suggestions

Consolidate the answer-concealment guidance: state the rule once in 'The core rule' and have the Good-and-bad-turns and Never-list entries reference it rather than restate it, trimming roughly 5-10 lines.

The 'Good and bad turns' and 'Never list' tables overlap on two rows (showing answers early, predicting hire/pass); merging the overlapping rows into a single contrastive table would remove the remaining repetition without losing the few-shot value.

DimensionReasoningScore

Conciseness

The body is terse, imperative, and assumes Claude's competence — no concept explanations, and information-dense tables for host forms, modes, judgment buckets, and good/bad turns. It falls just short of the anchor-5 'every token earns its place' because the answer-concealment rule is stated three times ("Never show any part of an answer before the learner has answered", the Good-and-bad-turns row "Asks the prompt and stops", and the Never-list pair "Never show an answer part before the reply"), which is trimmable redundancy; this matches anchor 4 ('minor instances of over-explanation that could be trimmed') rather than 5.

4 / 5

Actionability

As an instruction-only skill, its guidance is fully concrete: exact repo paths and a raw.githubusercontent fallback URL for the bank, a mode-selection table with an explicit tie-break rule, enumerated grade level-words ("missed, partial, working or strong"), explicit pick ordering ("a gap that is due, then an item never asked, then an item with the lowest last grade"), setup defaults, and edge-case handling ("If the learner says they do not know, ask once what they would measure first... grade 0 and go on"). Specific directives cover every common case, matching the anchor-5 standard for an instruction skill.

5 / 5

Workflow Clarity

Question mode is an explicitly numbered 8-step sequence where every step carries a "Done when:" exit criterion — explicit validation checkpoints — and step 8 verifies the state-file rows were appended (a post-write check on the one mutating operation, which the Never-list additionally constrains to append-only). Error-recovery branches are spelled out (no clone → raw file URLs; empty card → offer another card; stuck learner → grade 0 and continue), matching the anchor-5 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

The 290-line SKILL.md is an overview plus the core question loop, with all detail pushed to six real reference files (grading.md, state-file.md, scenario-mode.md, loops.md, routing.md, testing.md — all present in the bundle), each linked inline at its point of use and again in a "Read it when" table. A grep of the reference files confirms none of them reference further reference files, so references are exactly one level deep with clear navigation, matching the anchor-5 example structure.

5 / 5

Total

19

/

20

Passed

Description

100%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 is a model example: third-person voice, a fully enumerated concrete action loop (ask, wait, grade, follow up, route, record), and an explicit ten-phrase trigger list that answers 'when' unambiguously. It is dense but every clause carries capability or trigger information, with no fluff or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full workflow: "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", and "keeps an append-only record in INTERVIEW-LEARNING.md". This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' — the ask/wait/grade/route/record loop is fully enumerated with no coverage gaps, so it is above the level-4 anchor ('minor gaps in coverage').

5 / 5

Completeness

Both 'what' and 'when' are explicit: the what is the concrete coaching loop (ask, wait, grade, follow-ups, route gaps, record), and the when is an explicit "Trigger phrases:" clause listing ten concrete triggers — the equivalent of the anchor-5 'Use when... with concrete trigger phrases' pattern. The completeness cap of 3 for missing trigger guidance does not apply, and the 'when' is more explicit than the anchor-4 example.

5 / 5

Trigger Term Quality

Ten natural trigger phrases are given, including "interview prep", "mock interview", "ask me an interview question", "practise for my AI engineering interview", "run an incident scenario", "debugging round", "system design round", and "how ready am I for the interview" — phrasings a user would naturally say, with synonyms covering prep/practise/mock, question/scenario/round/loop, and review/readiness intents. This is comprehensive natural-term coverage in the anchor-5 sense (file extensions do not apply to this skill type), above the level-4 anchor's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche — mock interview coaching for AI engineering roles on a specific book's interview bank — and every trigger is interview-scoped ("mock interview", "review my interview gaps", "inference engineer loop"); even "debugging round" and "system design round" are standard interview-loop terms within that niche. Conflict risk with a general tutoring or system-design skill is minimal, matching the anchor-5 'clear niche with distinct triggers' rather than the level-4 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

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

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.