← Interview TrixCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Interview Trix
Snapshot Sep 30, 2026 · 23:11 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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.",
"included_files": [],
"name": "score-resume-for-a-job",
"skill_md_contents": "---\nname: score-resume-for-a-job\ndescription: 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.\n---\n\n# Score a resume against a job\n\nRun Interview Trix ATS on a resume the user already owns. Do not invent an ATS score.\n\n## Inputs\n\n- A resume: `res_…` id, a title, or \"latest\" / \"my resume\" (then `list_resumes`).\n- 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.\n\n## Steps\n\n1. 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.\n2. Call `score_resume_ats` with `resumeId` and `jobDescription` when you have a JD.\n3. Report the numeric score, up to a few top issues (fail/warn), and the ATS editor link from the tool.\n4. Only call `get_resume` if they also want specific rewrite suggestions from the actual bullets. Do not dump the full resume unless they asked.\n5. 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).\n\n## Errors\n\n- `resume_not_found`: list resumes and ask which id to use. Never guess another user's resume.\n- `upgrade_required` or ATS not on the plan: show the upgrade URL; do not fake a score.\n- Do not email the report or post it publicly.\n\n## Output\n\nPlain-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`).\n"
}SHA-256 of public snapshot: 40e01bbee968c2f4f08526e91084cb4621c2205d4e4ba971bbce239d77146eb6