Turrior AI Recruiter

View saved version →

---
name: turrior-applicant-report
description: Find, count, rank, or summarize applicants for a Turrior job when the user asks for candidate lists or recruiting reports.
---

Use this skill for applicant lists, counts, top candidates, recent applicants, green candidates, and recruiting reports.

1. If the job is named but its ID is unknown, resolve it with `list-short-job-posts`.
2. Applicants come from two sources. Call `get-candidates` separately with:
   - `interactionType: "application"`
   - `interactionType: "externalApplication"`
3. Merge both result sets unless the user explicitly asks to see the sources separately.
4. When the user asks for all stages, explicitly pass all supported funnel statuses rather than relying on the server default.
5. For counts, use `limit: 1` and sum the returned `total` values from both applicant sources.
6. For green candidates use `minScore: 75`.
7. For top candidates use `sortBy: "score"`.
8. Format the result as a concise Markdown recruiting report.
9. If evaluation requires quiz responses, use `get-quiz-answers` for text quizzes or `get-video-quiz-answers` for video quizzes based on the quiz type.

View saved version →

---
name: turrior-create-job
description: Create and optionally publish a Turrior job post when the user asks to create, post, or publish a vacancy.
---

Use this skill when the user wants to create a new Turrior job post.

1. Gather the missing job details in one concise message. Always determine the recruiting location before calling `create-new-job`.
2. Location rules:
   - Maximum 5 countries.
   - A city may be used only with exactly one country.
   - `onsite` requires both country and city.
   - "Worldwide" or "no restriction" means no `countryIds`.
3. Never guess dictionary IDs:
   - category → `search-categories`
   - country → `search-countries`
   - city → `find-city`, using the country's lowercase ISO2 `countryCode`
4. If a city search is ambiguous, ask the user to choose.
5. Call `create-new-job` only when the user has asked to create the job. Include all information already available rather than creating an unnecessarily incomplete draft.
6. If the user wants the job published, call `publish-job`. If required fields are missing, explain what must be completed.
7. After creation, offer to create and attach a video quiz with at least one introductory question about the candidate and their relevant experience. Explain that it can provide additional information for candidate scoring.
8. After successful publication, retrieve the job if necessary and return its public application URL:
   `https://turrior.com/apply/{slug}`

View saved version →

---
name: turrior-invite-interview
description: Invite a Turrior candidate to a Calendly interview when the user asks to schedule or send an interview invitation.
---

Use this skill when the user wants to invite a candidate to an interview.

1. Resolve the candidate and obtain their current application `interactionId`. Raw invitations cannot be used.
2. Call `get-calendly-event-types` before sending the invitation.
3. If the user named an interview type, select the closest matching Google Meet event type.
4. If no type was specified, use the first suitable event type.
5. If no Google Meet event type exists, tell the user that Calendly needs a suitable Google Meet event type configured.
6. Call `invite-candidate-to-interview` using the application `interactionId` and selected event URI.
7. If the MCP response reports `calendlyUnauthorized`, tell the user that their Calendly account needs to be reconnected.

View saved version →

---
name: turrior-manage-candidate
description: Change a candidate's hiring status, add a note, or add a talent to the Turrior shortlist.
---

Use this skill when the user asks to move, reject, hire, hold, shortlist, or add a note to a candidate.

1. If the candidate was provided by name, resolve and confirm them first using the candidate-resolution workflow.
2. Use IDs according to their exact meaning:
   - funnel change → application/interaction ID
   - candidate note → interaction ID
   - shortlist → `talent.id`
3. Do not use raw invitations with `change-candidates-status` or `add-candidate-note`.
4. For status changes, call `change-candidates-status` with the resolved application IDs and requested target status.
5. Check the result for partial transition failures and report them clearly.
6. For notes, call `add-candidate-note`.
7. For shortlist requests, call `add-to-shortlist`.
8. Never report an action as completed unless the corresponding MCP action succeeded.

View saved version →

---
name: turrior-manage-job
description: Find and manage an existing Turrior job when the user asks to edit, publish, unpublish, inspect, or get the application link for a vacancy.
---

Use this skill for operations on an existing job post.

1. Resolve a named job with `list-short-job-posts`.
2. If several jobs could match, ask the user which one they mean.
3. Before modifying the job, always call `get-full-job-post`.
4. For edits, call `patch-job` with only the fields the user requested to change.
5. Resolve category, country, and city IDs with their dictionary tools; never guess IDs.
6. Use `publish-job` or `un-publish-job` only when the user's request calls for that action.
7. For an application link, verify that the job is active and has a slug, then return:
   `https://turrior.com/apply/{slug}`

View saved version →

---
name: turrior-resolve-candidate
description: Identify and confirm a Turrior candidate when the user refers to an applicant or candidate by name.
---

Use this skill whenever another Turrior workflow needs to identify a candidate from their name.

1. Never perform an action on a name without resolving it first.
2. Search with `get-candidates`, `limit: 100`, and all supported funnel statuses so late-stage candidates are included.
3. Search one name token at a time:
   - If first and last name are given, search the last name first.
   - If no match, retry with the first name.
4. Do not use `interactionType`, job, date, score, or other filters unless the user's request requires them.
5. If both searches fail, call `get-candidates` again without `search`, with `limit: 100`, `sortBy: "date"`, `orderDirection: "DESC"`, and all funnel statuses. Scan the returned names before reporting no match.
6. If exactly one candidate matches, confirm using their name, job title, and current status before continuing.
7. If several candidates match, list them numbered with job title and status and ask the user to choose. Never choose for the user.
8. If no candidate matches, report that plainly and offer to list recent candidates.
9. After confirmation, reuse the resolved `talentId`, `userId`, `interactionId` and `jobId` as appropriate for the rest of the conversation.

View saved version →

---
name: turrior-screening-quiz
description: Create, update, or attach a text or video screening quiz to a Turrior job.
---

Use this skill when the user asks to create or manage candidate screening questions or a video interview quiz.

1. Choose `create-quiz` for text questionnaires and `create-video-quiz` for asynchronous video interviews.
2. When attaching an existing quiz, resolve it with `get-quizzes-list`, resolve the job if needed, then call `attach-quiz`.
3. Make the quiz skippable only when the user requests it or the workflow clearly requires it.
4. For video quizzes, include clear job-relevant questions. For a general candidate screening video, include at least one introductory question asking the candidate to introduce themselves and describe relevant experience.
5. `put-quiz` and `put-video-quiz` are full replacements, not patches. When updating, preserve the IDs of existing questions/options that should remain and send the complete final question list.
6. Never omit an existing question from an update unless it should be deleted.