Update to FaceFirst Interview Builder

{
  "description": "Prepare a FaceFirst job description and interview questions. Save an employer-reviewed job draft when requested.",
  "included_files": [],
  "name": "prepare-interview",
  "skill_md_contents": "---\nname: prepare-interview\ndescription: Prepare a FaceFirst job description and interview questions. Save an employer-reviewed job draft when requested.\n---\n\n# Prepare a FaceFirst interview\n\nPrepare a job draft for an asynchronous video interview. Candidates answer each question with a short video.\n\nUse the employer's role, duties, and requirements. Ask for missing facts only when they affect the questions.\nMark other missing facts as \"Not specified\". Do not invent pay, qualifications, experience, or work conditions.\n\nKeep the job description and requirements separate. Prepare up to ten clear questions about the stated duties.\nUse five questions unless the employer requests another count. Ask one question per video response.\nPrefer specific work examples that a candidate can explain in about 60 seconds.\nFor each question, explain what work evidence it seeks. Keep this explanation outside the saved question text.\nUse the same questions for candidates who apply for the same role.\n\nShow the title, description, requirements, questions, and missing facts before a save.\nKeep candidate assessment and decisions outside this workflow. Do not request candidate videos or personal records.\n\n## Save the draft\n\nWhen the employer requests a save, use the FaceFirst MCP connection.\nCall `get_profile` and `list_organizations` to identify the account and permitted organization.\nEach connection permits one organization. Ask the employer to select another connection if the organization is incorrect.\nIf the employer has not reviewed the prepared content, request that review before the save.\nAn explicit instruction to save the displayed content supplies the review approval.\n\nCall `create_job_draft` with the reviewed title, description, requirements, and question text.\nGenerate a unique `requestKey` with at least 16 letters, digits, underscores, or hyphens.\nKeep this key with the saved content. Reuse both for an identical retry after a timeout or uncertain result.\nUse a new key when the employer requests changed content as a new draft.\nFor a request-key conflict, show the error. Do not silently change the key and create another job.\n\nReport a save only after the tool returns the job ID and review URL.\nShow the review URL so the employer can open the draft in FaceFirst.\nExplain that the employer must publish the draft in FaceFirst before candidates can apply.\nUse `get_job_draft` to reopen a saved draft. Use `list_job_drafts` when the job ID is unknown.\n\nIf the connection is unavailable, provide the prepared content in the conversation.\nState that the draft was not saved. Do not invent a job ID or link.\nIf access has expired, ask the employer to reconnect FaceFirst.\nDo not request a password, token, or authentication code in the conversation.\n\nThe plugin cannot publish jobs, send invitations, purchase credits, or make candidate decisions.\nDo not describe those operations as plugin capabilities.\n"
}