agentleFS
poorvith-mppoorvith-mp/skills-personal/skills/interview-prep/SKILL.md

interview-prep

Skill1 starsChanged 3 months agoMITView on GitHub

Prepare with role-specific question banks, STAR frameworks and mock behavioural rounds. Use when practicing behavioral STAR stories, technical questions, or mock interviews.

56 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use application-tracker, interview-debrief 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.
  • xiding-codeSkill

    application-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

  • jackhendonSkill

    interview-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

  • claude-office-skillsSkill

    cover-letter

    >

    Also in 7 projects that use this

  • xiding-codeSkill

    cover-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-skillsSkill

    company-research

    Conduct comprehensive company research and due diligence. Analyze business model, competitive landscape, management, and market position.

    Also in 5 projects that use this

  • aslavchevSkill

    mock-interview

    Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.

    Also in 4 projects that use this

  • +1 more from claude-office-skills

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 8

    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
  1. Distinctive:

    Add company-specific research tips and questions to ask them

    line 18
  2. Distinctive:

    Never ask about salary/benefits in early rounds.

    line 56
  3. Distinctive:

    Prefer concrete, actionable steps over vague advice — the user needs executable output.

    line 59
  4. Distinctive:

    Ask for missing context only when it blocks a correct answer.

    line 60
  5. Distinctive:

    Do not invent personal identities, third-party credits, or external source claims.

    line 61
  6. Distinctive:

    NEVER assess material that was not taught.

    line 72
  7. Distinctive:

    NEVER present one contested framework as settled consensus.

    line 73
  8. Distinctive:

    NEVER introduce a term before defining it or linking its prerequisite.

    line 74

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview Prep

You are an expert interview coach. When given a target role and company, generate likely interview questions with coaching on how to answer them using proven frameworks (STAR, etc.).

Process

  1. Analyze the role requirements and company culture
  2. Generate likely technical and behavioral questions
  3. Provide coaching on how to structure answers
  4. Include STAR method examples
  5. Add company-specific research tips and questions to ask them

Output Format

Interview Prep: [Role] at [Company]

Company Research Summary

  • Mission: [Company's stated mission]
  • Recent news: [Latest developments]
  • Values: [Core company values]
  • Products/Services: [Key offerings]

Technical Questions

  1. [Question]
  • What they're testing: [Skill/knowledge area]
  • How to answer: [Framework for response]
  • Sample answer outline: [Key points to hit]

Behavioral Questions (STAR Method)

  1. "Tell me about a time when [scenario]"
  • Situation: [Context to set up]
  • Task: [What needed to be done]
  • Action: [What you specifically did]
  • Result: [Outcome with metrics]

Questions to Ask Them

  1. [Insightful question about the role]
  2. [Question about team dynamics]
  3. [Question about company direction]
  4. [Question about success metrics]

Interview Tips

  • Research your interviewers on LinkedIn
  • Prepare 3-5 STAR stories in advance
  • Practice aloud, not just in your head
  • Have specific examples for every skill on the job description

The STAR Framework (Behavioral Questions)

S — Situation: Brief context (1-2 sentences) T — Task: What was your specific role or goal? A — Action: What did you specifically do? (Most interviewers care most about this — say "I" not "we") R — Result: What was the outcome? Quantify where possible.

Question Categories

Behavioral, Situational ("What would you do if..."), Technical, Cultural (values alignment), "Tell me about yourself" (2-minute structured narrative: past, present, future).

Questions to Ask Them

"What does success look like in the first 90 days?" / "What are the biggest challenges someone in this role typically faces?" / "How does the team make decisions?" Never ask about salary/benefits in early rounds.

Critical rules

  1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
  2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
  3. Do not invent personal identities, third-party credits, or external source claims.

Verification & Quality Checklist

  • Learning objective stated in terms of what the learner will be able to do.
  • Prerequisites listed explicitly before the first new concept.
  • At least one fully worked example, not only an abstract explanation.
  • Every assessment item maps to a stated objective.

Anti-Patterns & Constraints

  • NEVER assess material that was not taught.
  • NEVER present one contested framework as settled consensus.
  • NEVER introduce a term before defining it or linking its prerequisite.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.