跳到正文
cccskills
免费在 GitHub 公开

interview-scheduling

Prepare interview scheduling drafts by matching Greenhouse interview plans with every panelist’s calendar. Produce two or three available time options, a candidate email, and individual invitation drafts for a coordinator to review and send.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Daily interview-scheduling sweep for {{projectName}}. Reads {{greenhouse_pipeline}} for candidates ready to schedule and each one's interview plan, checks {{interviewer_calendars}} for panel availability, and drafts a candidate slot proposal plus a calendar invite per interviewer to {{coordinator_review_inbox}}. Never sends a proposal or invite and never makes a hiring decision; a coordinator confirms and sends everything.

查看安装方法

适用场景

  • Prepare daily interview scheduling drafts
  • Find time slots available to every interviewer
  • Redraft proposals after interview plans change
  • Prepare candidate emails and interviewer invitations

包含的文件(1)

  • SKILL.md5.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

<skill name="interview-scheduling"> <overview> Coordinating an interview loop means combining two systems that don't talk to each other: the interview plan — who's on the panel, which round, how long it runs — lives in Greenhouse, and whether those people are actually free lives in their calendars. A daily sweep reads both, proposes a time that works for every panelist, and drafts the candidate-facing proposal and each interviewer's invite.

Fresh session every run, no local ledger: the agent recomputes the batch from {{greenhouse_pipeline}}'s current state and {{interviewer_calendars}}'s current availability each time, so what "already scheduled" means is whatever {{greenhouse_pipeline}} already shows for that candidate. </overview>

<when-to-load> - The daily scheduling cron fires. - A human asks the agent to schedule or re-propose a specific candidate's next round. - An interview plan or a panelist's availability changes and the prior proposal needs to be redrafted. </when-to-load> <workflow>

Step 1 — Find candidates ready to schedule

Read {{greenhouse_pipeline}} for every candidate marked ready to schedule — cleared their current stage and waiting on the next round — who doesn't already have a drafted or confirmed proposal for that round. Skip anyone already scheduled or already carrying an undrafted proposal from a prior run.

Step 2 — Read the interview plan

For each candidate, pull the plan for their next round from {{greenhouse_pipeline}}: which interviewers are on the panel, what the round covers, and how long it's scheduled to run. This plan is the only source of truth for who belongs on the invite — never add or drop a panelist on your own judgment.

Step 3 — Check the panel's real availability

Check every interviewer on the plan against {{interviewer_calendars}} for open slots in the next several business days that fit the round's duration. A slot only counts if it's free for every panelist on the plan — partial availability is not a proposable slot. Surface 2–3 candidate slot options where the full panel is clear.

Step 4 — Draft the candidate proposal

Draft a proposal email to the candidate offering the 2–3 open slots from Step 3, naming the round and roughly what to expect, in a tone that reads like a coordinator wrote it. Place it in {{coordinator_review_inbox}}. This is a draft only — it does not go to the candidate until the coordinator sends it.

Step 5 — Draft the calendar invites

For the same slots, draft a calendar invite per interviewer on the panel — correct attendees, round name, and duration from the plan — and place the drafts in {{coordinator_review_inbox}} alongside the candidate proposal. Do not create a live calendar event; these are drafts for the coordinator to issue once a slot is confirmed with the candidate.

Step 6 — Hand the batch to the coordinator, stop

Place the full batch — one proposal and one set of draft invites per candidate — in {{coordinator_review_inbox}}, each with the candidate's name, round, and proposed slots. Do not send the proposal. Do not send or create any calendar invite. Do not change the candidate's stage, add a note that implies a decision, or touch anything in {{greenhouse_pipeline}} beyond reading the plan.

</workflow> <guardrails> - **Never send.** Every candidate proposal and every calendar invite is held in {{coordinator_review_inbox}} for the coordinator to review, adjust, and send or issue themselves. The agent has no send action and no action that creates a live calendar event. - **Plan-only panel.** The interviewers on a draft invite come strictly from {{greenhouse_pipeline}}'s interview plan for that candidate and round — never a panelist added or substituted on the agent's own judgment. - **Full-panel availability only.** A slot is only proposed if every panelist on the plan is free for it. Partial availability is never proposed as if it were a confirmed option. - **No hiring decisions, ever.** The agent never rejects a candidate, advances or skips a stage, or drafts or sends an offer. It has no action that changes a candidate's hiring status. - **Fresh per run.** Each sweep recomputes ready-to-schedule candidates and panel availability from the current state of {{greenhouse_pipeline}} and {{interviewer_calendars}} — no assumption carries over from the prior run. - **Scoped secrets.** Access to {{greenhouse_pipeline}} and {{interviewer_calendars}} is brokered through connectors; no raw credential is ever pasted into chat. </guardrails> </skill>

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

中文简介正在准备中。当前显示英语简介。

  • Reviewing GitHub repository access requests from Slack
  • Preparing AWS IAM permissions for a specific task
  • Routing sensitive access requests for additional review
kortix-ai/suna2万2026年10月18日 更新

Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.

中文简介正在准备中。当前显示英语简介。

  • Research a prospective customer before outreach
  • Prepare background information for meeting attendees
  • Compare a competitor's products and positioning
kortix-ai/suna2万2026年10月18日 更新

Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.

中文简介正在准备中。当前显示英语简介。

  • Checking whether campaign budgets are being spent on schedule
  • Investigating rising acquisition costs or falling ad returns
  • Finding ads and keywords that spend without converting
kortix-ai/suna2万2026年10月18日 更新

Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.

中文简介正在准备中。当前显示英语简介。

  • Automate form entry and page navigation
  • Capture screenshots and extract page data
  • Explore web apps for bugs
kortix-ai/suna2万2026年10月18日 更新

Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.

中文简介正在准备中。当前显示英语简介。

  • Checking incoming invoices against purchase orders
  • Finding duplicate invoices and likely resends
  • Reviewing unit prices and remaining order balances
kortix-ai/suna2万2026年10月18日 更新

billing

免费

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

中文简介正在准备中。当前显示英语简介。

  • Update billing logic and its specification together
  • Review how trials and enterprise contracts are handled
  • Find the code that defines prices and allowances
kortix-ai/suna2万2026年10月18日 更新

查看 kortix-ai 的全部技能

报告此技能的问题