interview-prep
Skill1 starsChanged 7 months agoMITView on GitHub
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
56 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- fancyboi999/ai-engineering-from-scratch-zhtheir own version, first seen Nov 8, 2026
- rohitg00/ai-engineering-from-scratchtheir own version, first seen Nov 8, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- Gianni03/jobtracker-skillstheir own version, first seen Nov 8, 2026
- surfmind-space/awesome-surfmindtheir own version, first seen Nov 8, 2026
- ong6/skillstheir own version, first seen Nov 5, 2026
Used with
Projects with it also use application-tracker, interview-debrief and 10 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.
xiding-codeSkillapplication-tracker
Automatically log and track all job applications submitted. Use this skill after every application submission to record the details in a tracking spreadsheet and save relevant documents. Also trigger when the user asks "application status", "what have I applied to", "tracking", or wants to review their application history. Maintains a single source of truth for all job search activity.
Also in 4 projects that use this
jackhendonSkillinterview-debrief
Structure notes from a user research session into a clean debrief with insights, quotes, and implications. Paste your raw notes in and get a formatted summary ready for Notion.
Also in 3 projects that use this
proficientlyjobsSkilljob-search
Search for jobs matching my resume and preferences
Also in 9 projects that use this
claude-office-skillsSkillcover-letter
>
Also in 7 projects that use this
xiding-codeSkillcover-letter-writer
Write and iteratively refine cover letters using a 3-agent debate team (2 Opus critics + 1 Sonnet judge). Use this skill whenever a job application allows cover letter upload, whenever the user asks to write or improve a cover letter, or whenever the job-screener skill returns APPLY for a position. The must-write rule (if enabled in config) applies: if the application system has a cover letter upload field, a cover letter MUST be written. Trigger on: "write cover letter", "cover letter", any application form with a cover letter upload option, or after a job-screener APPLY decision.
Also in 3 projects that use this
claude-office-skillsSkillcompany-research
Conduct comprehensive company research and due diligence. Analyze business model, competitive landscape, management, and market position.
Also in 5 projects that use this
- +1 more from claude-office-skills
Other versions56 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- anthropics/knowledge-work-plugins★ 35k18% same
Wrote their own version · 55
- rohitg00/ai-engineering-from-scratch★ 78ksame name
- tinyfish-io/tinyfish-cookbook★ 2.3ksame name
- ShenSeanChen/waku-agent★ 2ksame name
- fancyboi999/ai-engineering-from-scratch-zh★ 1.3ksame name
- jerry-ai-dev/MODULAR-RAG-MCP-SERVER★ 1.2ksame name
- lan1177/interview-prep★ 92same name
- matyasstoch/david-skills★ 59same name
- muggl3mind/career-manager★ 24same name
- jaskirat1616/grok-skills★ 22same name
- JayRHa/agent-skills★ 12same name
45 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.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Create comprehensive interview plans with competency-based questions, structured scorecards, and evaluation rubrics.
- Distinctive: line 70
Create a structured scorecard with:
- Distinctive: line 155
Action: Create a 30-minute phone screen scorecard assessing leadership style, technical depth, team building, and motivation alignment.
- Distinctive: line 160
Use the same questions for all candidates at the same stage to ensure fair comparison.
- Distinctive: line 162
Write behavioral anchors for each score level before the interview, not after.
“Common” is measured: kept by at least 6 in 10 of the 48 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
Create comprehensive interview plans with competency-based questions, structured scorecards, and evaluation rubrics. Ensure consistent, fair, and effective candidate assessment.
Workflow
Step 1: Define the Interview Structure
Based on the role and stage, determine:
- Core competencies to assess (3-5 per interview round):
- Technical skills specific to the role
- Problem-solving and analytical thinking
- Communication and collaboration
- Leadership and influence (for senior roles)
- Culture alignment and values fit
- Interview format:
- Phone screen (30 min): Culture fit, motivation, basic qualifications
- Technical (45-60 min): Skills assessment, problem-solving, domain knowledge
- Behavioral (45 min): Past experience, competency-based questions
- Hiring manager (45 min): Team fit, growth trajectory, mutual evaluation
- Executive (30 min): Strategic thinking, leadership, company alignment
- Panel (60 min): Cross-functional assessment with multiple interviewers
Step 2: Generate Competency-Based Questions
For each competency, create 2-3 questions using the STAR format (Situation, Task, Action, Result):
Structure each question with:
- The primary question
- 2-3 follow-up probes to go deeper
- What a strong answer includes (green flags)
- What a weak answer looks like (red flags)
- How the question maps to the competency being assessed
Question types to include:
- Behavioral: "Tell me about a time when..."
- Situational: "How would you handle..."
- Technical: Role-specific problem-solving
- Motivation: "Why this role / company / domain"
- Values: Questions that reveal decision-making principles
Step 3: Build the Scorecard
Create a structured scorecard with:
- Each competency rated on a 1-4 scale:
- 1 = Does not meet expectations
- 2 = Partially meets expectations
- 3 = Meets expectations
- 4 = Exceeds expectations
- Behavioral anchors for each rating level
- Space for evidence and specific examples
- Overall recommendation: Strong Hire / Hire / No Hire / Strong No Hire
Step 4: Add Logistics and Guidelines
Include interviewer guidance:
- Opening script (put candidate at ease, explain the format)
- Time allocation per question section
- Legal compliance reminders (questions to avoid)
- Candidate question time (reserve last 5-10 minutes)
- Debrief instructions and timeline
Output Format
## Interview Plan: [Role] — [Stage]
**Duration**: [X] minutes
**Competencies Assessed**: [list]
**Interviewer**: [name/TBD]
### Opening (5 minutes)
- Welcome and introductions
- Explain the interview format
- [Customize based on stage]
### Questions
#### Competency 1: [Name] (XX minutes)
**Q1**: [Primary question]
- Probe: [Follow-up 1]
- Probe: [Follow-up 2]
- Green flags: [What strong answers include]
- Red flags: [What weak answers look like]
**Q2**: [Primary question]
- Probe: [Follow-up 1]
- Green flags: [indicators]
- Red flags: [indicators]
#### Competency 2: [Name] (XX minutes)
[Same structure]
### Candidate Questions (5-10 minutes)
Reserve time for the candidate to ask questions.
### Closing (2 minutes)
- Thank the candidate
- Explain next steps and timeline
---
## Scorecard
| Competency | 1 (Below) | 2 (Partial) | 3 (Meets) | 4 (Exceeds) | Score | Evidence |
|------------------------|-----------|-------------|-----------|-------------|-------|----------|
| [Competency 1] | [anchor] | [anchor] | [anchor] | [anchor] | | |
| [Competency 2] | [anchor] | [anchor] | [anchor] | [anchor] | | |
| [Competency 3] | [anchor] | [anchor] | [anchor] | [anchor] | | |
**Overall Recommendation**: [ ] Strong Hire [ ] Hire [ ] No Hire [ ] Strong No Hire
**Key Strengths**:
**Key Concerns**:
**Additional Notes**:Examples
User: "Create an interview plan for a Senior Frontend Engineer, technical round." Action: Build a 60-minute technical interview covering React architecture, performance optimization, system design, and code quality. Include coding prompts and evaluation rubrics.
User: "I need behavioral interview questions for a Product Manager." Action: Generate STAR-format questions covering stakeholder management, prioritization, data-driven decision making, and cross-functional leadership.
User: "Scorecard for an engineering manager phone screen." Action: Create a 30-minute phone screen scorecard assessing leadership style, technical depth, team building, and motivation alignment.
Best Practices
- Limit each interview round to 3-5 competencies. Trying to assess everything in one session leads to shallow evaluation.
- Use the same questions for all candidates at the same stage to ensure fair comparison.
- Include at least one question that tests for learning agility, not just existing knowledge.
- Write behavioral anchors for each score level before the interview, not after.
- Remind interviewers to avoid illegal questions about age, family status, religion, national origin, disability, or marital status.
- Time-box each section. Without structure, interviewers spend too long on early questions and rush the end.
- Include a "candidate questions" section. What candidates ask reveals priorities and preparation.
- For technical interviews, prefer questions that mirror actual job tasks over abstract puzzles.
- Debrief should happen within 24 hours while memory is fresh. Scorecards completed days later are unreliable.
- Calibrate interviewers periodically. Different interviewers using the same scorecard should produce similar ratings for the same candidate performance.
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.

