interview
Skill3 starsChanged 52 days agoMITView on GitHub
Use this skill when the candidate has an interview coming or wants to get BETTER at interviewing — e.g. "prep me for Anthropic", "I have a phone screen Thursday", "drill me", "mock interview for Writer", "what will they ask?", "what questions should I ask them?", "they'll probably worry about my short tenure", "hype me up, it's in an hour", "I keep bombing final rounds", "here's my interview recording", "the recruiter sent feedback", "start a training plan". Owns role prep briefs, live mock drilling, question banking, post-round debriefs, and transcript analysis.
94 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisdesmondSML/chris-skillstheir own version, first seen Nov 8, 2026
- Firzus/agent-skillstheir own version, first seen Nov 8, 2026
- claude-code-hardened/claude-code-hardenedtheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- codewhale-hq/codewhale-plugin-marketplacetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use fetch-library-docs, contributor and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Rehan-Ul-HaqSkillfetch-library-docs
Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.
Also in 4 projects that use this
NimbleBrainIncSkillcontributor
Get started contributing to NimbleBrain open source — find an integration to build, set up your environment, propose an idea, or check on your work. Use when onboarding as a contributor. Triggers include "I'm a new contributor", "what should I build", "show me open issues", "file an issue".
Also in 3 projects that use this
mjunaidcaSkillbrowsing-with-playwright
Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction. NOT when only fetching static content (use curl/wget instead).
Also in 4 projects that use this
qa-amanSkillteach-me
Teach a topic, video, article, codebase change, spec, or transcript until the user demonstrably understands it, using staged instruction, a running checklist doc, and quizzes. Use whenever the user says "teach me", "explain this in detail", "help me understand X", "/teach-me", "walk me through this", "I want to learn X", "understand this deeply", or pastes a YouTube URL, article, paper, PR, or spec and asks to understand it rather than summarize it. Also use when the user wants study notes or raw material from a source they are learning. Do NOT use for a quick factual lookup, a summary request, or when the user just wants the answer.
Also in 8 projects that use this
trebaudSkillfind-unknowns
Workflow for surfacing a task's unknowns before, during, and after implementation — blind spot pass, brainstorm/prototype, interview, references, implementation plan, deviation notes, quiz. Use when starting work in an unfamiliar domain or codebase, when a task feels underspecified, when the user says "find my unknowns", "blindspot pass", "what am I missing", "help me scope this", or when a long task came back wrong.
Also in 3 projects that use this
donatassimkusSkilloffer
Offer design, pricing strategy, and business model architecture. Invoke when asked about making an offer better, pricing a product or service, naming an offer, raising prices, generating fast cash, increasing lifetime value, finding the right customer, qualifying buyers, or designing a business model where customers pay for their own acquisition. Use when someone says their offer isn't converting, they need to charge more, they want to add bonuses or guarantees, or they need a money model for their business.
Also in 3 projects that use this
Other versions94 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 94
- claude-code-best/claude-code★ 23ksame name
- Q00/ouroboros★ 6.3ksame name
- Hisn00w/ASu-skills★ 6.1ksame name
- boshu2/agentops★ 453same name
- genkovich/sdd★ 187same name
- jvm-skills/jvm-skills★ 140same name
- kv0906/pm-kit★ 138same name
- tobieapb/claude-interactive-documentation-workflow★ 105same name
- panaversity/claude-code-skills-lab★ 57same name
- roman01la/skills-agents★ 48same name
84 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 80 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Never Sharpen: Keep vague signals honest.
- Distinctive: line 38
Verified Claims: Verify company and interviewer intelligence via public professional URLs (never personal data).
- Very specific: line 65
Update story use counts in storybank.md.
- Very specific: line 87
Session close: Run ../profile/scripts/check_files.mjs --workspace ..
- Distinctive: line 91
Never fabricate interview process details, panel identities, or past questions without verified citations.
- Distinctive: line 92
Never deploy struck claims or unconfirmed story details into spoken candidate scripts.
“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview — prep, live drill & debrief
Goal
The candidate walks into every interview prepared and continuously builds interview mastery. Scored rounds are evaluated honestly at the candidate's seniority band. Records compound across prep briefs, practice logs, question banks, and story use counts. Scored by references/eval.md.
| Must be true | Where |
| Brief on file with current header metadata for scheduled interviews | prep/<company_key>-<title_key>.md |
Predicted questions categorized (banked, researched with cites, generated [inferred]) | brief ## Predicted questions |
| 5 reverse questions to ask with purpose and reversal triggers | brief ## Questions to ask |
| Day-of cheat sheet closes the brief | brief ## Day-of cheat sheet |
| Scored rounds logged: coach score first, band stated, self-assessment delta recorded | session file · practice-log.md |
| Real interview debrief leaves 4 writes (capture, log row, banked questions, story use counts) | session file · practice-log.md · question-bank.md · storybank.md |
| Question bank holds real questions asked of candidate (vague kept vague) | question-bank.md |
| Stated comp numbers and concessions routed to owner files | negotiation/ · base-resume.md § Claim rules |
Prerequisites
- Required: Workspace
CLAUDE.md(none → profile's Setup);profile.md(seniority band);jd-analysis/<key>.mdfor role prep (suggestevaluatefirst if absent). - Optional:
company/<slug>.md,storybank.md(8+ confirmed stories for retrieval drills),question-bank.md,contacts/<company>.md,courses/.
Loops and sequences
Brief construction, gated ladder, round mechanics, and root-cause diagnostics live in references/patterns.md.
The brief (a sequence)
Runs when an interview is coming (candidate request, coach routing, or inbox sweep detection).
- Question Hierarchy: Banked questions from
question-bank.mdoutrank generated questions. Researched questions carry inline citations; inferred questions carry[inferred]. - Never Sharpen: Keep vague signals honest; do not fabricate specific questions as verified.
- Verified Claims: Verify company and interviewer intelligence via public professional URLs (never personal data).
- Grounded Mapping: Map questions to confirmed
storybank.mdstories. Never deploy a struck claim frombase-resume.md § Claim rules.
Exits with the brief persisted to prep/ and day-of sheet highlighted in chat.
The drill (the loop)
Runs when candidate asks to practice, rep is due, or an upcoming interview warrants a live mock.
- Standard: 5 dimensions at candidate's seniority band (
references/eval.md). - Budget: Stated scored rounds per session. Read top of
practice-log.mdbefore round 1. - Each round: Unscored warmup $\rightarrow$ question $\rightarrow$ answer $\rightarrow$ coach scores first $\rightarrow$ candidate self-scores $\rightarrow$ delta feedback with Interviewer's Read $\rightarrow$ ONE assigned change for next round.
- Obligations:
- Score first: Evaluate before asking candidate's read (calibration gap is core coaching signal).
- State band: Always evaluate against candidate's stated band.
- Synthetic label: Mark composite drills synthetic.
- Exits: Stage gate met, or session completed with Scoreboard row on top of
practice-log.md; or the ceiling: 3+ stagnant sessions on a dimension → stop volume and diagnose root cause (references/eval.md § Root-cause taxonomy).
The debrief (a sequence)
Runs when candidate reports back from a real interview.
- Emotional check-in $\rightarrow$ capture notes.
- Four writes in same turn:
- Capture file:
practice/<date>-real-<company>.md(transcript or Q&A capture). - Append round record to
practice-log.md. - Bank questions to
question-bank.md(vague recall kept vague). - Update story use counts in
storybank.md.
- Capture file:
- Route stated comp numbers to
negotiation/<company>.mdand conceded claims tobase-resume.md § Claim rules.
Exits with all 4 writes persisted to disk.
The satellites
| Ask / Scenario | Runs when | Exits with |
| Questions to ask | "what should I ask them?" | 5 reverse questions in brief (purpose, round, reversal) |
| Concern counters | "they'll worry about X" | 3-part counter framing for anticipated risks |
| Day-of confidence | "hype me up, it's in an hour" | 10-minute warm-up reel and focus cue (no generic fluff) |
| Mock interview | "mock interview for X" | Banked/predicted questions, curveball, hire signal, top 3 changes, 2 writes |
| Training plan | "start a training plan" | Weakness profile, 10–15 min daily reps |
| Transcript analysis | Recording/transcript provided | Relevance > Substance > Structure > Credibility scores, weakest answer rewritten |
| Presentation coaching | "help me with my presentation" | Communication arc, structure, and 10-question Q&A drill |
State
Owned: prep/, practice/, practice-log.md, question-bank.md, composite-target.md, negotiation/ (shapes in references/schema.md).
- Hands back: Thin storybank →
storybank; TMAY re-tuning →profile; missing course →learn; funnel pattern →coach. - Session close: Run
../profile/scripts/check_files.mjs --workspace .. No checker-subagent is spawned (coach voice). Report outcomes, never narration (clean is 1 line; fix FAILs before reply ends).
Guardrails
- Never fabricate interview process details, panel identities, or past questions without verified citations.
- Never deploy struck claims or unconfirmed story details into spoken candidate scripts.
- Fabricated answers in drills are a red flag to address directly, not polish.
- Comp coaching boundaries: record stated figures; never invent counter-offers.
Every reply ends with ONE contextual next step — a sentence with its why, not a menu.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

