Interview Trix

View saved version →

---
name: manage-resumes
description: Use when the user wants to list Interview Trix resumes, open or inspect one, import or create a resume draft from chat, pick a template, collect intake, optimize or retarget, fix the same resume in place, or get a PDF. After they pick a template name (Meridian) or id, immediately call create_resume_draft — do not only say it is selected. Never ask for a screenshot. For ATS after create, offer score_resume_ats when the user agrees. Do not use for starting a mock or interview reports unless they ask separately.
---

# Manage Interview Trix resumes

Use Interview Trix resume tools only. Never invent resume content the user did not provide. Never email, publish, or delete resumes.

Keep calling tools until a resume exists and you return the Interview Trix editor link. Do not stop at “template selected”.

After any successful `create_resume_draft` or `update_resume_draft`, treat the returned `resumeId` as the **active resume for this chat** until the user picks another or asks for a new document.

**Never ask the user to call tools by name, paste a `resumeId`, or type MCP parameters.** They speak in plain language; you choose the tool and pass the active `resumeId` from the last successful create/update in this chat (or resolve via `list_resumes` if unclear).

## What the user says → what you do

The user does **not** know tool names. Map their words to actions:

| User says (text or voice) | You do |
|---------------------------|--------|
| “Add Node.js, TypeScript, MongoDB to my skills” / “update skills with…” | `update_resume_draft` on the **active `resumeId`** with `skills` (+ align last two `experience` bullets and `projects` if they asked to match) |
| “Fix the title to Forward AI Engineer” / “wrong subtitle” | `update_resume_draft` with `personalInfo.jobTitle` (+ `targetRole` if set) on active id |
| “Update the resume you just made” / “change this one” | `update_resume_draft` on active id — **never** `create_resume_draft` again |
| “Give me the link” / “where is my resume” (especially in voice) | Read **`Editor link (copy or open):`** and `voiceSummary.speakableUrl` from the **last successful** create/update tool result; if none in this chat, `list_resumes` and offer the latest or ask which title |
| “Create a new resume for [role]” | `start_resume_flow` → path → template → create (not silent retarget) |
| “Use my saved resume for this role” | `list_resumes` → `get_resume` → `create_resume_draft` with `creationMode: "retarget"` |
| “Score it for ATS” / “yes, run ATS” | `score_resume_ats` with active `resumeId` + stored JD from research |

After every update in voice, say in plain language what you did (e.g. “I added Node.js, TypeScript, MongoDB, PostgreSQL, and Pinecone to your skills and aligned your last two roles”) **and** read the full editor URL from the tool output once.

## Widget cards are the CTA (inline UI)

ChatGPT renders each widget-bearing tool (`start_resume_flow`, `list_resume_templates`, `start_resume_intake`, `create_resume_draft`, `update_resume_draft`) as an inline card **directly above** your follow-up text — you cannot move it below. So:

- Put any explanation **before** you call the tool. The card is the action surface the user taps/fills/submits.
- Call **exactly one** widget tool per turn (run read-only tools like `list_resumes` / `get_resume` first, then the one widget tool).
- After the card renders, keep text to **one short line**. Do **not** restate the template list, the four paths, or the editor/ATS buttons — they are in the card. Duplicating them buries the CTA.
- Never say "use the picker above" unless this turn actually rendered one.

## Start here (mandatory when creating or importing)

1. Call `start_resume_flow` or `list_resumes` when the user wants a **new** or **imported** resume.
2. Ask **one** path question (or use the path widget):
   - **Retarget saved resume** — `get_resume` → `create_resume_draft` with `creationMode: "retarget"`, `sourceResum

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: prepare-for-a-job
description: Use when the user pastes a job description or asks to get interview-ready, prepare for a company or role, check their Interview Trix plan or remaining mock-interview credits, or wants ATS feedback plus a mock interview. Also use for "can I start an interview" and "what plan am I on". For building or retargeting a resume after role research, use manage-resumes. Do not use for PDF-only, resume import-only, or past interview reports.
---

# Prepare for a job on Interview Trix

Help the signed-in user get ready for a specific job using Interview Trix tools. The live interview always happens on Interview Trix, never inside this chat.

## When to stop immediately

- They ask to delete an account, wipe resumes, email a recruiter, or post a resume publicly: refuse. Interview Trix cannot do that.
- They want you to conduct the full mock interview in this chat: refuse the live Q&A. Create the interview with tools, then send the join link.

## Steps

1. Call `get_entitlements`. Summarize plan, remaining credits, and whether AI mock interviews and ATS are allowed. If they only asked about plan or credits, stop after this step.
2. If they shared a job description (JD), keep it for ATS. If they want ATS or a mock and there is no JD, ask for the JD or target role before creating an interview.
3. Call `list_resumes`. If they need a resume for this role:
   - Call `start_resume_flow` (or ask one path question): retarget saved resume, brand-new from scratch, upload file, or merge attachment into saved resume — follow `manage-resumes`.
   - If none exist and they chose from scratch: `list_resume_templates`, then `start_resume_intake` if facts are missing, then `create_resume_draft` with `creationMode: "fresh"` and `factsProvenance: "intake"`.
   - If optimizing a saved resume: `create_resume_draft` with `creationMode: "retarget"`, `retargetDepth: "deep"`, `sourceResumeId`, `targetRole`, and `jobDescription` (50+ chars).
   - In voice: map plain requests (“add skills”, “give me the link”) to tools — see **manage-resumes** voice section. Never ask the user to name tools or paste `resumeId`.
   - Reuse contact details already collected in this chat; do not re-ask header unless missing.
   - Do not start a mock yet.
4. If they want content-level advice (rewrite bullets, match keywords), call `get_resume` with that `resumeId`. Do not call `get_resume_pdf` unless they asked for a file.
5. If ATS is in scope (they pasted a JD or asked to score), call `score_resume_ats` with `resumeId` and `jobDescription`. Report the score, top issues, and the ATS editor link. On `upgrade_required`, show the upgrade URL and stop the interview step.
6. Ask before creating a mock. If they agree and mocks are allowed with enough credits, call `initialize_mock_interview` with `role` (from the JD or user), optional `targetCompany`, `jobDescription`, `resumeId`, and duration 15 unless they have Tech Pro or Enterprise and asked for 30 minutes. Language `en` unless they asked for Hindi (`hi`).
7. Give the interview join URL. State clearly: start the mock on Interview Trix; this chat cannot run the live interview.

## Output

- Plan and credits in one short line when relevant.
- Which resume you used (`title` + `resumeId`).
- ATS score and editor link when scored.
- Interview join link only after a successful `initialize_mock_interview`.
- On `resume_not_found`, call `list_resumes` and ask which one to use.

View saved version →

---
name: review-interview-results
description: Use when the user asks about past Interview Trix mock interviews, overall score, strengths, improvements, or a detailed report. Triggers include "how did I do", "my interviews", "interview report", "intv_" id. Do not use to start a new mock, score a resume, or download a resume PDF.
---

# Review interview results

Show the user's own Interview Trix interview history and reports. Do not invent scores.

## Steps

1. If they did not pass `interviewId` (`intv_…`), call `list_interviews`. Summarize role, status, date, and score when present. Offer the report or join link from the tool.
2. For a completed interview they care about, call `get_interview_report` with that `interviewId`.
3. Summarize overall score, category scores, strengths, and improvements in plain language. Include the full report link from the tool.
4. If the interview is not completed, say the report is not ready. Point them at the join/resume link from `list_interviews` if they still need to finish on Interview Trix.

## Errors

- `interview_not_found`: it is not in their account. List interviews; do not probe other users.
- `report_not_ready`: they must finish the mock on Interview Trix first.
- `upgrade_required` (detailed reports): show the upgrade URL; you may still list interviews and basic scores from `list_interviews`.

## Refusals

Do not start a new mock here unless they explicitly ask (then `start-mock-interview`). Do not email the report or post it publicly.

View saved version →

---
name: score-resume-for-a-job
description: Use when the user wants an ATS score, keyword gaps, or to tailor a resume to a job description. Triggers include "ATS", "score my resume", "how does this match this JD", "keywords missing". Do not use for creating a mock interview, importing a new resume, or PDF download unless they also asked for those separately.
---

# Score a resume against a job

Run Interview Trix ATS on a resume the user already owns. Do not invent an ATS score.

## Inputs

- A resume: `res_…` id, a title, or "latest" / "my resume" (then `list_resumes`).
- A job description or target role. If they asked to score against a job and there is no JD, ask for the JD. You may still score without a JD if they only want a general ATS check.

## Steps

1. If `resumeId` is missing, call `list_resumes`. Use the named resume, else the most recently updated. If the list is empty, follow `manage-resumes` intake in chat — do not invent an ATS score or call `create_resume_draft` empty.
2. Call `score_resume_ats` with `resumeId` and `jobDescription` when you have a JD.
3. Report the numeric score, up to a few top issues (fail/warn), and the ATS editor link from the tool.
4. Only call `get_resume` if they also want specific rewrite suggestions from the actual bullets. Do not dump the full resume unless they asked.
5. Do not call `initialize_mock_interview` unless they clearly asked to start a mock after scoring. If they did, follow `start-mock-interview` (credits first).

## Errors

- `resume_not_found`: list resumes and ask which id to use. Never guess another user's resume.
- `upgrade_required` or ATS not on the plan: show the upgrade URL; do not fake a score.
- Do not email the report or post it publicly.

## Output

Plain-language score, what to fix first, and the Interview Trix ATS link. Mention `hasPdf` only if they asked for a file (then use `get_resume_pdf`).

View saved version →

---
name: start-mock-interview
description: Use when the user wants to start, create, or practice an AI mock interview on Interview Trix for a role or company. Also use for "can I interview", remaining interview credits, 15 vs 30 minutes, or Hindi vs English mock. Do not use for past reports, ATS-only scoring, or resume PDF.
---

# Start a mock interview

Create a draft AI mock on Interview Trix and send a join link. Do not run the live interview in this chat. Do not pretend to be the interviewer after the link is created.

## Steps

1. Call `get_entitlements`. If AI mock is not allowed or credits are insufficient, explain that, show the upgrade URL when the tool provides one, and stop.
2. Confirm `role` (job title). If missing, ask. Optional: years of `experience`, `targetCompany`, `jobDescription`, `language` (`en` or `hi`).
3. **Ask the user to pick the duration — never choose it yourself and never default to 30.** Call `start_interview_flow` (pass `role`, and `targetCompany`/`jobDescription` if known). On ChatGPT this shows a 15/30 picker widget; on other clients ask one short question ("15 or 30 minutes?"). Wait for their choice. 30 is only offered on Tech Pro/Enterprise. Only skip this step if the user already stated a specific duration in their request.
4. Resolve a resume: `resumeId` they gave, else `list_resumes` (newest or named). If there is no resume, follow `manage-resumes` intake (collect details in chat, then `create_resume_draft`). Do not start the mock until a resume exists.
5. After the user picks a duration, call `initialize_mock_interview` with `role`, that chosen **`duration`**, **`resumeId`** (use the active resume from this chat when they just created one), and optional `jobDescription`, `targetCompany`. **Do not** send `department` or `discipline` unless the user gave an exact allowed value — omitting them is fine.
6. Only say the interview was created after the tool returns `success: true` with `interviewId` and a join URL. If the tool errors, explain the error — do not pretend it worked.
7. In the **same reply**, paste the full join URL from `Join link (copy or open):` and the `interviewId`. Do not tell the user to ask again for the link. The actions widget may also show a Start interview button.
8. Say they must open Interview Trix to take the interview (camera/mic on that site).

## After create

- Do not fire interview questions in this chat.
- If they want history or a score from a finished session, use `review-interview-results` instead.

## Errors

- `upgrade_required`: show upgrade link; do not create the interview.
- `resume_required` / empty resume: send them to create or edit a resume first.
- Never start a mock for someone else's resume id; `resume_not_found` means list theirs and ask.