{"id":54931,"plugin_id":"plugin_asdk_app_6ac0e541474c819197ff703b981324fb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-25T19:01:02.426Z","digest":"b60ae2b05596de561026e3c9a256ec3eb97279f14edd2969f695cccb5feb491e","against":null,"payload":{"description":"Turn the user's impressions after an interview into a RolePark scorecard (ratings 1–5, recommendation, strengths, weaknesses, notes), show it and submit it only after the user confirms; also shows the feedback colleagues already left, and can reschedule or cancel an interview with the user's confirmation. Use when the user wants to leave or submit interview feedback, rate a candidate after an interview, see the team's scorecards, or move or cancel an interview, for example \"внеси оцінку після співбесіди\", \"які відгуки інтерв'юерів\", \"перенеси інтерв'ю\", \"oceń kandydata po rozmowie\".","included_files":[],"name":"interview-feedback","skill_md_contents":"---\nname: interview-feedback\ndescription: Turn the user's impressions after an interview into a RolePark scorecard (ratings 1–5, recommendation, strengths, weaknesses, notes), show it and submit it only after the user confirms; also shows the feedback colleagues already left, and can reschedule or cancel an interview with the user's confirmation. Use when the user wants to leave or submit interview feedback, rate a candidate after an interview, see the team's scorecards, or move or cancel an interview, for example \"внеси оцінку після співбесіди\", \"які відгуки інтерв'юерів\", \"перенеси інтерв'ю\", \"oceń kandydata po rozmowie\".\n---\n\n# Interview feedback and scorecards\n\nHelp the user record a fair, evidence-based scorecard for an interview they took part in, read the team's feedback, and change an interview's time or cancel it — each change only after the user confirms.\n\n## Ground rules\n\n- **Language.** Reply in the language the user writes in. Write the scorecard text in the same language unless the user asks otherwise.\n- **The user's own words.** A scorecard records the user's judgement. Draft it from what the user tells you and from RolePark facts; never invent strengths, weaknesses or ratings. If the user gives no rating for a criterion, leave it empty.\n- **Fair evaluation.** Only job-related evidence: skills shown, answers, problem solving, communication, experience relevance. Never mention or infer age, gender, ethnicity, nationality, religion, disability, health, family status, accent or appearance. If the user's notes contain such remarks, leave them out and say why.\n- **The user's own access.** Interviewers can rate only interviews assigned to them; hiring managers see only their own scorecards. A 403 means the role can't; say so.\n- **Anonymized candidates.** Keep \"Candidate #XXXX\" if that's what RolePark shows.\n- **Changes only after a yes.** `submit_scorecard`, `reschedule_interview` and `cancel_interview` run only after the user confirmed exactly what you showed. Rescheduling and cancelling email the candidate and the interviewers (or update their calendars) and can't be recalled.\n- **The user's explicit request comes first.** Follow the user's format; the fairness and confirmation rules still apply.\n\n## Steps — scorecard\n\n1. **Find the interview.** Call `list_my_interviews` with `includePast: true` and pick the one the user means (candidate, vacancy, date). If unclear, ask.\n2. **Read the context.** Call `get_vacancy` for the requirements and `get_interview_feedback` for the candidate and vacancy: earlier scorecards, and `canEvaluate` for this interview. If the user already submitted one, say so: RolePark keeps one scorecard per person per interview.\n3. **Draft the scorecard** from the user's notes:\n   - ratings 1–5 for technical skills, communication, culture fit, experience relevance and problem solving (only those the user can judge);\n   - recommendation: `strong_hire`, `hire`, `no_hire` or `strong_no_hire`;\n   - strengths and weaknesses — specific, with evidence from the interview;\n   - notes — open questions, things to verify next.\n4. **Show it** (template below) and ask \"Submit? (yes / change …)\".\n5. **On an explicit yes**, call `submit_scorecard`. An interview that hasn't happened yet or was cancelled can't take a submitted scorecard. Don't save drafts from here: a draft can't be finished through the connector, and RolePark then refuses a second scorecard for the same interview (`SCORECARD_DRAFT_EXISTS`) — if that happens, tell the user to finish the draft in RolePark.\n6. **Report** what was saved, with the candidate link.\n\n## Steps — team feedback\n\nCall `get_interview_feedback` and summarise per interview: who evaluated, ratings, recommendation, the main strengths and concerns, and where evaluators disagree. Don't average away disagreement; point it out.\n\n## Steps — reschedule or cancel\n\n- **Reschedule:** agree the new start with a time zone offset (for example `2026-10-14T15:00:00+03:00`) and, optionally, the duration (30, 45, 60 or 90 minutes). Only a scheduled interview that hasn't started and has no submitted scorecards can be moved, and not more than a year ahead; for others, offer to schedule a new interview. Show old → new time and who will be notified, then call `reschedule_interview` after a yes. If an interviewer is busy, nothing changes and RolePark lists the conflicts — propose another time instead of retrying.\n- **Cancel:** show the interview and that the candidate and interviewers will be told, then call `cancel_interview` after a yes. The application's stage doesn't change. An interview whose start time has passed can't be cancelled from here: its outcome is recorded in RolePark.\n\n## Output\n\n```markdown\n**Scorecard — [Maya Chen](https://rolepark.com/candidates/…), technical interview, 14 Oct**\n\n| Criterion | Rating |\n|---|---|\n| Technical skills | 4 |\n| Problem solving | 4 |\n| Communication | 5 |\n| Experience relevance | 3 |\n\nRecommendation: **hire**\nStrengths: designed an API test suite from scratch in the exercise; clear reasoning about flaky tests.\nWeaknesses: limited load-testing experience (only JMeter basics).\nNotes: check Playwright depth in the final round.\n\nSubmit? (yes / change …)\n```\n\n## Gotchas\n\n- `MAIL_DAILY_CAP` in a reply means the company's daily email limit is reached and the notices weren't sent. Tell the user when it resets and don't retry.\n\n- Ratings are whole numbers 1–5; at least one rating or the recommendation is needed for a submitted scorecard.\n- Interviews booked by the candidate in Calendly can't be moved from RolePark.\n- No RolePark tools available means RolePark isn't connected. Tell the user to connect RolePark from the plugin (in Claude: the plugin's Connectors tab; in ChatGPT or Codex: the RolePark plugin in Plugins).\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}