agentleFS
Miracle-AlignerMiracle-Aligner/job-search-hq/.claude/skills/interview-prep/SKILL.md

interview-prep

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the user wants to prepare for an interview tracked in Job Search HQ. Triggers: /interview-prep, "prep me for the X interview", "interview prep for <company>", "help me get ready for my final round", or accepting the prompt offered by /update-status when an interview is scheduled. Researches the company live and builds one brief with everything needed to pass, tailored to the candidate's profile + CV and the JD, and stores it on the event (events[].prep).

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use application-tracker, job-search 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

  • rhowardstoneSkill

    job-search

    Search for jobs across multiple boards and company career pages. Use when looking for new positions to apply to.

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

    company-research

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

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

  • rhowardstoneSkill

    apply

    Research-backed job application workflow emphasizing relationship-building over mass applications

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 1

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

    Keep it tight and skimmable (headers + bullets).

    line 43
  2. Very specific:

    Write the markdown to the target event's prep field in data/vacancies.json (vacancies[i].events[j].prep).

    line 47
  3. Very specific:

    Idempotent: if prep already exists on that event, show the user a diff/summary and ask whether to refresh (regenerate with newer research) …

    line 51

“Common” is measured: kept by at least 6 in 10 of the 51 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

Produce one self-contained brief that gives the candidate everything to walk in prepared. Invoked standalone (/interview-prep <id> [eventId]) or from /update-status when an interview is scheduled.

Inputs (read these first)

  • The vacancy in data/vacancies.json — role, JD recap (summary, plus, minus), score/ss, statusDetail, the target event (stage, time, via, interviewer if noted).
  • profile/candidate.md + profile/profile.json — strengths, gaps, comp/level targets.
  • The CV digests (/ingest-cv) — concrete projects, metrics, evidence to cite.
  • Live research — WebSearch + WebFetch the company: what they do, product, stage/funding, recent news (last ~6 months), tech signals, Glassdoor-style interview-format hints. Cite nothing you didn't actually find; mark unknowns as unknown.

The brief (markdown → events[].prep)

Tailor depth to the stage (HR screen = light; tech/final = deep). Cover:

  1. Company snapshot — what they do, product, stage/size, 2–3 recent developments.
  2. Role & JD recap — the 3–5 things this role actually needs; how the candidate maps.
  3. Stage & format — what this round is (recruiter / tech / system design / final), who's on it if known, likely structure and length.
  4. Likely questions — behavioral + technical, tailored to the JD stack and the candidate's gaps. Make them specific to this company/role, not generic.
  5. Strong talking points — mapped to concrete CV evidence (project, metric, outcome).
  6. Gap defense — for each real gap (from the profile), an honest, confident framing.
  7. Smart questions to ask them — sharp, role/company-specific.
  8. Comp & level context — the candidate's target band vs this role; a negotiation anchor.
  9. Logistics — date/time, via, meeting URL, what to have open.

Keep it tight and skimmable (headers + bullets). It's a cheat-sheet, not an essay.

Persist

Write the markdown to the target event's prep field in data/vacancies.json (vacancies[i].events[j].prep). If no specific event, attach to the soonest upcoming interview-kind event, or create a follow-up event to hold it and say so.

Idempotent: if prep already exists on that event, show the user a diff/summary and ask whether to refresh (regenerate with newer research) or keep — don't silently duplicate.

The viewer renders prep as a collapsible "Interview prep" block on the card with copy-to-clipboard.

Finish

python3 scripts/validate.py
python3 scripts/build.py --real

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.