Skip to content
Skills Library
Personal productivity · Learning & explanation

prep

/prep

Prepares the user for a job interview with WorkHunt interview prep (likely questions, a company brief, recruiter-screen scripts) and can run a short mock interview. Use when the user has an interview or screen coming up for a job they are tracking or tailored for, or asks to prep, practise or rehearse for an interview.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Prepares the user for a job interview with WorkHunt interview prep (likely questions, a company brief, recruiter-screen scripts) and can run a short mock interview. Use when the user has an interview or screen coming up for a job they are tracking or tailored for, or asks to prep, practise or rehearse for an interview.

Arguments

/prep [company or role]
Original author description

Prepares the user for a job interview with WorkHunt interview prep (likely questions, a company brief, recruiter-screen scripts) and can run a short mock interview. Use when the user has an interview or screen coming up for a job they are tracking or tailored for, or asks to prep, practise or rehearse for an interview.

How it works

  1. Workflow
  2. Rules
Original SKILL.md headings · 27 lines, 576 words
SKILL.md preview
---
name: prep
description: "Prepares the user for a job interview with WorkHunt interview prep (likely questions, a company brief, recruiter-screen scripts) and can run a short mock interview. Use when the user has an interview or screen coming up for a job they are tracking or tailored for, or asks to prep, practise or rehearse for an interview."
argument-hint: "[company or role]"
---

# Prepare for an interview

Get the user ready for a specific interview using the prep WorkHunt already holds for their tailored session.

## Workflow

1. Find the tailoring session. If a `sessionId` returned by tailor_resume is already in this conversation and matches the job, use it. Otherwise call list_applications and match the company or role from $ARGUMENTS or from the conversation, case-insensitive. If totalCount is larger than the first page, page through until you have seen every application. Use the matching application's `sessionId`. If several applications match, ask which one. If none matches, or the match has no `sessionId`, explain that prep is built from a tailored session, offer to tailor the resume to the posting first (the tailor workflow), and stop.
2. Call get_interview_prep(sessionId) first. It never generates anything and never spends anything.
3. If `questions`, `companyBrief` or `recruiterScripts` are null or empty, tell the user you are generating prep and that each call takes around 25 seconds, then call generate_interview_prep(sessionId). While `pending` is non-empty, call it again with `sections` set to `pending`. Stop after 4 calls in total and give the `openUrl` if anything is still pending.
4. If a tool says prep needs a WorkHunt pass, relay that in plain words with any link it contains and stop.
5. Summarise for the user:
   - the three to five most useful points from `companyBrief`;
   - the top five likely questions, one line each on what a strong answer covers, using the question's own guidance where present.
   Mention that the other sections exist (recruiter scripts, day-of checklist, technical challenges, resume coaching) without dumping them, and show any of them in full if asked.
6. Offer a short mock interview. If the user accepts, ask one question at a time from the generated questions, wait for their answer, then give brief feedback: what landed, what to tighten, and one concrete improvement, judged against that question's guidance and the company brief. Move on when the user is ready. Stop when they say so and end with a two-line summary of their strengths and the one thing to practise.
7. End with the `openUrl` link so the user can review the prep in WorkHunt.

## Rules

- Tools are named by their bare names (get_interview_prep, generate_interview_prep, list_applications, tailor_resume). Depending on the client they carry a prefix such as mcp__plugin_workhunt_workhunt__ or a connector prefix; any WorkHunt tool with the matching bare name is the right one. If no WorkHunt tools are available at all, tell the user to connect WorkHunt: run /mcp in Claude Code and sign in to "workhunt", or in claude.ai enable the WorkHunt connector under Settings > Connectors. Do not try to do the task another way.
- Never delete anything. There are no delete tools; deleting and editing resume content happen in the WorkHunt app.
- A WorkHunt tool error is written for the user (for example "Set a baseline resume first ...", a daily limit, or "needs a WorkHunt pass"). Relay it in plain words, include any link it contains, and do not retry the call.
- End with the WorkHunt link the last relevant tool returned (`openUrl`, `tailorUrl`, `editUrl` or `trackerUrl`) so the user can review or continue in WorkHunt.
- Dates go to tools as ISO 8601 (YYYY-MM-DD).
- Never invent facts about the company beyond the brief. If the user asks something the brief does not cover, say the brief does not cover it and suggest where they could check.

Versions

RepositoryScoreLicence
This page · coffeedroplabs/workhunt-claude-plugin100MIT
web3illy/private-second-brain-skills100MIT
alirezarezvani/gaios100MIT

Database snapshot: 13.11.2026 · package version 8ccba4eaaca7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90canada-interview-prep
    Prepare for a Canadian job interview with likely questions, STAR answers built from the user's own experience, and a mock interview. Use when the user says "I have an interview", "help me prepare", "mock interview", or "what will they ask".
  • 90interview-prep
    Prepare the user for an interview for one of their job applications. Reads the application issue (job description, first impressions, earlier /interview notes) and writes prep notes, likely questions, and questions to ask, as a comment on the issue. Use when the user has an…
  • 90us-interview-prep
    Prepare for a US job interview - behavioral STAR answers, likely questions, mock interview, and offer negotiation (base, bonus, equity, benefits). Use when the user says "I have an interview", "behavioral questions", "mock interview", "negotiate my offer", or "is this offer good" for a US job.
  • 100interview-prep
    Prepares a candidate for a specific job interview — generating likely questions, coaching STAR-method stories, drilling behavioral and role-specific answers, and producing smart questions to ask back. Use this skill when a user asks to "help me prep for an interview", "what…
  • 100interview-prep
    Prepare for a specific job interview. Researches the company, analyzes the role, maps the user's real experience to it, predicts likely questions (plus the next ring of topics out), and produces a concise interview brief and a one-page card to keep in view during the call, then…
  • 90interview-prep-coach
    Prepare a candidate for an interview using their real experience. Builds STAR stories mapped to the role, likely questions including the awkward ones about their gaps with how to answer each, and sharp questions to ask, with an optional mock-interview mode. Use when the user has…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.