agentleFS
Sign inStart free
DevabubakarDevabubakar/atsprep-skills/skills/interview-prep/SKILL.md

interview-prep

Skill0 starsChanged 22 days agoMITView on GitHub

Run a mock job interview with ATSPrep's question bank - pick likely questions from the job post and resume, ask them one at a time, and give STAR-based feedback with a stronger version of each answer. Use when someone has an interview coming up, wants likely interview questions, wants to practise answers, or asks to improve a specific answer.

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

  • proficientlyjobsSkill

    job-search

    Search for jobs matching my resume and preferences

    Also in 9 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use whichever is available, in this order:

    line 18
  2. Very specific:

    ATSPrep MCP tools: If the ATSPrep MCP server (https://atsprep.com/mcp) is connected, call its tools by name.

    line 20
  3. Very specific:

    Ask for the job title and, ideally, the job post (for a link, use fetch_job_post) and their resume.

    line 32
  4. Very specific:

    Call interview_questions with what you have (job_description, resume_text) and limit around 8.

    line 33
  5. Distinctive:

    Keep feedback short and specific.

    line 41
  6. Distinctive:

    Never tell the user to claim experience they don't have.

    line 42

“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

A mock interview, one question at a time. ATSPrep's web version, with spoken practice, is at https://atsprep.com/tools/interview-questions.

How to call ATSPrep

Use whichever is available, in this order:

  1. ATSPrep MCP tools. If the ATSPrep MCP server (https://atsprep.com/mcp) is connected, call its tools by name. Some clients add a prefix, e.g. mcp__atsprep__check_resume.
  2. The bundled script (needs Node 18+ and network access):
    node scripts/atsprep.mjs <tool> key=value key=@path/to/file.txt
    key=@file sends a file's text, which is the safe way to pass a resume or job post. Write the user's text to a file in the current working directory first, and delete it when you're done. node scripts/atsprep.mjs list lists the tools.
  3. Plain HTTPS (no Node): POST JSON-RPC to https://atsprep.com/mcp with headers Content-Type: application/json and Accept: application/json, text/event-stream, and the body {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"<tool>","arguments":{...}}}.

Arguments and limits for every tool are in references/tools.md. What leaves the machine is in references/privacy.md. Tell the user before sending their text to an AI tool the first time.

Steps

  1. Ask for the job title and, ideally, the job post (for a link, use fetch_job_post) and their resume.
  2. Call interview_questions with what you have (job_description, resume_text) and limit around 8. With neither, it returns common questions; tailor them to the job title yourself. Use kind (posting, resume, about, behavioural, role or closing) to focus on one group if the user asks.
  3. Share the STAR tips the tool returns in a few lines, then ask one question and wait for the answer. Don't list every question unless asked.
  4. Call review_interview_answer (AI) with question, answer and kind: story for "tell me about a time", pitch for "tell me about yourself", plan for "how would you...", number for salary, close for "any questions for us?". Share what worked, what was missing (situation, task, action, result) and the stronger version. If the AI part was skipped, the rule-based feedback still applies.
  5. Let them retry or move on. At the end, sum up their two or three biggest patterns.

Coaching rules

  • The stronger answer may only use facts from the user's own answer. If a result needs a number, ask what it was.
  • Keep feedback short and specific. One fix per answer beats ten.
  • Never tell the user to claim experience they don't have.

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.

Check your setup, free