[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739VACN2T85C2KB1YVW7NAF":3,"skill-same:01M739VACN2T85C2KB1YVW7NAF":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M739VACN2T85C2KB1YVW7NAF","interview-scheduler",null,"Design and coordinate efficient interview processes with optimal panel composition, scheduling logistics, and candidate experience","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Finterview-scheduler\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: interview-scheduler\ndescription: Design and coordinate efficient interview processes with optimal panel composition, scheduling logistics, and candidate experience\nlicense: MIT\nmetadata:\n  author: ClawFu\n  version: 1.0.0\n  mcp-server: \"@clawfu\u002Fmcp-skills\"\n---\n\n# Interview Scheduler\n\n> Design efficient interview processes with optimal panel composition, logical scheduling flow, and positive candidate experience.\n\n## When to Use This Skill\n\n- Setting up interview loops\n- Coordinating panel schedules\n- Designing interview stages\n- Optimizing candidate experience\n- Creating interview runbooks\n\n## Methodology Foundation\n\nBased on **structured interviewing best practices** and **candidate experience research**, combining:\n- Stage-appropriate assessment\n- Panel diversity requirements\n- Time-to-hire optimization\n- Candidate communication\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Designs interview stages | Final panel selection |\n| Suggests panel composition | Scheduling conflicts |\n| Creates question banks | Interview format (virtual\u002Fonsite) |\n| Drafts communications | Offer timing |\n| Identifies bottlenecks | Business priorities |\n\n## Instructions\n\n### Step 1: Define Interview Process\n\n**Stage Design:**\n\n| Stage | Purpose | Format | Duration |\n|-------|---------|--------|----------|\n| Phone Screen | Basic qualification | Remote | 30 min |\n| Technical | Skills assessment | Remote\u002FOnsite | 60 min |\n| Hiring Manager | Fit and depth | Remote\u002FOnsite | 45 min |\n| Team\u002FCulture | Team dynamics | Onsite | 45 min |\n| Executive | Final approval | Onsite | 30 min |\n\n**Process Variations:**\n\n| Role Level | Stages | Total Time |\n|------------|--------|------------|\n| Individual Contributor | 3-4 | 3-4 hours |\n| Manager | 4-5 | 5-6 hours |\n| Director+ | 5-6 | 6-8 hours |\n| Executive | 6+ | 8+ hours |\n\n### Step 2: Panel Composition\n\n**Panel Selection Criteria:**\n\n| Role | Include | Rationale |\n|------|---------|-----------|\n| Hiring Manager | Always | Final decision authority |\n| Direct Reports | If managing | Two-way assessment |\n| Cross-functional | Recommended | Collaboration preview |\n| Skip Level | Senior roles | Leadership alignment |\n| HR\u002FRecruiting | Screen\u002FFinal | Process consistency |\n\n**Diversity Requirements:**\n- Minimum 2 different perspectives on panel\n- Gender diversity when possible\n- Tenure diversity (new and experienced)\n- Function diversity for cross-team roles\n\n### Step 3: Schedule Optimization\n\n**Scheduling Principles:**\n1. Candidate availability first\n2. Minimize calendar fragmentation\n3. Allow buffer between interviews\n4. End with positive impression interview\n5. Same-day feedback when possible\n\n**Optimal Day Structure:**\n\n| Time | Interview | Why |\n|------|-----------|-----|\n| 9:00 | Technical | Fresh candidate, complex assessment |\n| 10:30 | Break | Decompression |\n| 11:00 | Hiring Manager | Core conversation |\n| 12:00 | Lunch | Culture signal, informal |\n| 1:00 | Team | Energy after lunch |\n| 2:00 | Executive | Final impression |\n\n### Step 4: Communication Templates\n\n**Key Touchpoints:**\n1. Interview confirmation\n2. Day-before reminder\n3. Day-of logistics\n4. Post-interview next steps\n5. Status updates\n\n### Step 5: Feedback Coordination\n\n**Debrief Structure:**\n- Schedule within 24 hours of final interview\n- Collect written feedback before meeting\n- Structured discussion format\n- Clear decision criteria\n- Documented outcome\n\n## Examples\n\n### Example 1: Full Interview Loop Design\n\n**Input:**\n```\nDesign interview process for:\n- Role: Senior Software Engineer\n- Team: 5 engineers, 1 manager\n- Timeline: Hire within 3 weeks\n- Format: Hybrid (some remote, some onsite)\n```\n\n**Output:**\n```\n## Interview Process: Senior Software Engineer\n\n### Process Overview\n\n| Stage | Format | Duration | Interviewers | Turnaround |\n|-------|--------|----------|--------------|------------|\n| 1. Recruiter Screen | Phone | 30 min | Recruiter | Same day |\n| 2. Technical Screen | Video | 60 min | Engineer | 24 hours |\n| 3. Onsite Loop | In-person | 4 hours | Panel | 24 hours |\n| 4. Debrief | Internal | 30 min | All | Same day |\n| 5. Offer | Call | 15 min | HM + Recruiter | 48 hours |\n\n**Total Timeline:** 10-14 business days\n\n---\n\n### Stage 1: Recruiter Screen\n\n**Format:** Phone\u002FVideo call\n**Duration:** 30 minutes\n**Interviewer:** Recruiter\n\n**Purpose:** Basic qualification, logistics, motivation\n\n**Questions:**\n1. Walk me through your background (5 min)\n2. Why are you interested in this role? (3 min)\n3. What's your ideal next role? (3 min)\n4. Salary expectations? (2 min)\n5. Timeline and availability? (2 min)\n6. Candidate questions (10 min)\n\n**Pass Criteria:**\n- [ ] Meets minimum experience (5+ years)\n- [ ] Reasonable salary alignment\n- [ ] Available within timeline\n- [ ] Genuine interest\n\n---\n\n### Stage 2: Technical Screen\n\n**Format:** Video call with code sharing\n**Duration:** 60 minutes\n**Interviewer:** Senior Engineer (Sarah)\n\n**Purpose:** Technical depth, problem-solving, code quality\n\n**Structure:**\n- 5 min: Introductions\n- 10 min: Technical background discussion\n- 35 min: Coding problem (medium difficulty)\n- 10 min: System design discussion\n- 5 min: Candidate questions\n\n**Assessment Areas:**\n| Area | Weight | Signals |\n|------|--------|---------|\n| Problem solving | 40% | Approach, communication |\n| Code quality | 30% | Clean, tested, efficient |\n| Technical depth | 20% | Language mastery, patterns |\n| Collaboration | 10% | Receptive to hints, explains well |\n\n**Pass Criteria:** Score 3+ on each area (1-5 scale)\n\n---\n\n### Stage 3: Onsite Loop (4 Hours)\n\n**Panel Composition:**\n\n| Time | Interview | Interviewer | Focus |\n|------|-----------|-------------|-------|\n| 9:00 | System Design | Tom (Staff Eng) | Architecture thinking |\n| 10:00 | Code Review | Lisa (Senior Eng) | Code quality, feedback |\n| 11:00 | Hiring Manager | Mike (Eng Manager) | Fit, growth, expectations |\n| 12:00 | Lunch | Any team member | Culture, informal |\n| 1:00 | Behavioral | Sarah (Senior Eng) | STAR examples |\n\n**Detailed Interview Guides:**\n\n#### System Design (Tom, 9:00-10:00)\n\n**Question:** \"Design a real-time notification system for a social media platform\"\n\n**Assessment:**\n| Criterion | What to Look For |\n|-----------|------------------|\n| Requirements gathering | Clarifies scale, features |\n| High-level design | Components, data flow |\n| Deep dive | Storage, queuing, delivery |\n| Trade-offs | Articulates decisions |\n| Scale | Handles growth scenarios |\n\n#### Code Review (Lisa, 10:00-11:00)\n\n**Exercise:** Review prepared PR with intentional issues\n\n**Assessment:**\n| Criterion | What to Look For |\n|-----------|------------------|\n| Bug detection | Finds logic errors |\n| Style feedback | Constructive, specific |\n| Security awareness | Identifies vulnerabilities |\n| Communication | Kind, actionable feedback |\n\n#### Hiring Manager (Mike, 11:00-12:00)\n\n**Topics:**\n1. Career trajectory and goals\n2. Management style preferences\n3. Conflict resolution examples\n4. Growth areas and learning\n5. Questions about team\u002Frole\n\n#### Behavioral (Sarah, 1:00-2:00)\n\n**STAR Questions:**\n1. \"Tell me about a time you disagreed with a technical decision\"\n2. \"Describe a project that failed and what you learned\"\n3. \"Give an example of helping a teammate grow\"\n4. \"Tell me about navigating ambiguity\"\n\n---\n\n### Stage 4: Debrief\n\n**Timing:** Same day, 4:00 PM\n**Attendees:** All interviewers + Recruiter\n**Format:** 30-minute structured discussion\n\n**Agenda:**\n| Time | Activity |\n|------|----------|\n| 0-5 | Written feedback review (pre-submitted) |\n| 5-20 | Round-robin: Each interviewer shares (3 min each) |\n| 20-25 | Discussion of concerns\u002Fquestions |\n| 25-30 | Decision: Strong Yes \u002F Yes \u002F No \u002F Strong No |\n\n**Decision Criteria:**\n- Strong Yes from HM required\n- No more than 1 \"No\" vote\n- Technical interviewers must be Yes+\n\n---\n\n### Communication Templates\n\n**Interview Confirmation:**\n```\nSubject: Interview Confirmation - Senior Software Engineer\n\nHi [Name],\n\nWe're excited to have you visit for your onsite interviews!\n\nDate: [Date]\nTime: 9:00 AM - 2:00 PM\nLocation: [Address]\n\nYour schedule:\n9:00 - System Design with Tom\n10:00 - Code Review with Lisa\n11:00 - Hiring Manager with Mike\n12:00 - Lunch with the team\n1:00 - Behavioral with Sarah\n\nPlease bring a laptop and valid ID. Parking validation available.\n\nReply to confirm or if you have any questions.\n\nBest,\n[Recruiter]\n```\n\n**Post-Interview Next Steps:**\n```\nSubject: Thank You & Next Steps\n\nHi [Name],\n\nThank you for spending time with our team today!\n\nOur team will be debriefing this afternoon, and you'll hear\nfrom us within 48 hours on next steps.\n\nIn the meantime, please don't hesitate to reach out with\nany questions.\n\nBest,\n[Recruiter]\n```\n```\n\n### Example 2: Quick Schedule Coordination\n\n**Input:**\n```\nNeed to schedule 4 interviews for tomorrow:\n- Candidates: Alice, Bob, Carol\n- Interviewers available: Mike (9-12), Sarah (10-2), Tom (11-4)\n- Each interview: 45 minutes\n```\n\n**Output:**\n```\n## Optimized Interview Schedule\n\n### Tomorrow's Schedule\n\n| Time | Mike | Sarah | Tom |\n|------|------|-------|-----|\n| 9:00 | Alice | - | - |\n| 10:00 | - | Bob | - |\n| 11:00 | Carol | - | Alice |\n| 12:00 | - | Carol | Bob |\n| 1:00 | - | - | Carol |\n\n### By Candidate\n\n| Candidate | Interview 1 | Interview 2 |\n|-----------|-------------|-------------|\n| Alice | Mike @ 9:00 | Tom @ 11:00 |\n| Bob | Sarah @ 10:00 | Tom @ 12:00 |\n| Carol | Mike @ 11:00 | Sarah @ 12:00 |\n\n### Notes\n\n- Alice: 2-hour gap between interviews (offer coffee\u002Fworkspace)\n- Bob: Back-to-back, efficient\n- Carol: Back-to-back, efficient\n\n### Calendar Invites Needed\n\n1. Alice + Mike: 9:00-9:45\n2. Bob + Sarah: 10:00-10:45\n3. Alice + Tom: 11:00-11:45\n4. Carol + Mike: 11:00-11:45\n5. Bob + Tom: 12:00-12:45\n6. Carol + Sarah: 12:00-12:45\n7. Carol + Tom: 1:00-1:45\n```\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Designing interview stages\n- Optimizing panel composition\n- Creating schedules\n- Drafting communications\n\n### What This Skill Cannot Do\n- Access actual calendars\n- Send invitations\n- Know interviewer preferences\n- Make hiring decisions\n\n## Iteration Guide\n\n**Follow-up Prompts:**\n- \"Create interview questions for [stage]\"\n- \"Draft the candidate rejection email\"\n- \"How should we handle scheduling conflict with [interviewer]?\"\n- \"Design a scorecard for [interview type]\"\n\n## References\n\n- Google re:Work Hiring Practices\n- Lever Interview Scheduling Guide\n- SHRM Interview Best Practices\n- Greenhouse Structured Interviewing\n\n## Related Skills\n\n- `resume-screener` - Pre-interview evaluation\n- `onboarding-guide` - Post-hire process\n- `employee-support` - New hire support\n\n## Skill Metadata\n\n- **Domain**: HR Operations\n- **Complexity**: Intermediate\n- **Mode**: cyborg\n- **Time to Value**: 30-60 min per role\n- **Prerequisites**: Role requirements, panel availability\n","# Interview Scheduler\n\n> Design efficient interview processes with optimal panel composition, logical scheduling flow, and positive candidate experience.\n\n## When to Use This Skill\n\n- Setting up interview loops\n- Coordinating panel schedules\n- Designing interview stages\n- Optimizing candidate experience\n- Creating interview runbooks\n\n## Methodology Foundation\n\nBased on **structured interviewing best practices** and **candidate experience research**, combining:\n- Stage-appropriate assessment\n- Panel diversity requirements\n- Time-to-hire optimization\n- Candidate communication\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Designs interview stages | Final panel selection |\n| Suggests panel composition | Scheduling conflicts |\n| Creates question banks | Interview format (virtual\u002Fonsite) |\n| Drafts communications | Offer timing |\n| Identifies bottlenecks | Business priorities |\n\n## Instructions\n\n### Step 1: Define Interview Process\n\n**Stage Design:**\n\n| Stage | Purpose | Format | Duration |\n|-------|---------|--------|----------|\n| Phone Screen | Basic qualification | Remote | 30 min |\n| Technical | Skills assessment | Remote\u002FOnsite | 60 min |\n| Hiring Manager | Fit and depth | Remote\u002FOnsite | 45 min |\n| Team\u002FCulture | Team dynamics | Onsite | 45 min |\n| Executive | Final approval | Onsite | 30 min |\n\n**Process Variations:**\n\n| Role Level | Stages | Total Time |\n|------------|--------|------------|\n| Individual Contributor | 3-4 | 3-4 hours |\n| Manager | 4-5 | 5-6 hours |\n| Director+ | 5-6 | 6-8 hours |\n| Executive | 6+ | 8+ hours |\n\n### Step 2: Panel Composition\n\n**Panel Selection Criteria:**\n\n| Role | Include | Rationale |\n|------|---------|-----------|\n| Hiring Manager | Always | Final decision authority |\n| Direct Reports | If managing | Two-way assessment |\n| Cross-functional | Recommended | Collaboration preview |\n| Skip Level | Senior roles | Leadership alignment |\n| HR\u002FRecruiting | Screen\u002FFinal | Process consistency |\n\n**Diversity Requirements:**\n- Minimum 2 different perspectives on panel\n- Gender diversity when possible\n- Tenure diversity (new and experienced)\n- Function diversity for cross-team roles\n\n### Step 3: Schedule Optimization\n\n**Scheduling Principles:**\n1. Candidate availability first\n2. Minimize calendar fragmentation\n3. Allow buffer between interviews\n4. End with positive impression interview\n5. Same-day feedback when possible\n\n**Optimal Day Structure:**\n\n| Time | Interview | Why |\n|------|-----------|-----|\n| 9:00 | Technical | Fresh candidate, complex assessment |\n| 10:30 | Break | Decompression |\n| 11:00 | Hiring Manager | Core conversation |\n| 12:00 | Lunch | Culture signal, informal |\n| 1:00 | Team | Energy after lunch |\n| 2:00 | Executive | Final impression |\n\n### Step 4: Communication Templates\n\n**Key Touchpoints:**\n1. Interview confirmation\n2. Day-before reminder\n3. Day-of logistics\n4. Post-interview next steps\n5. Status updates\n\n### Step 5: Feedback Coordination\n\n**Debrief Structure:**\n- Schedule within 24 hours of final interview\n- Collect written feedback before meeting\n- Structured discussion format\n- Clear decision criteria\n- Documented outcome\n\n## Examples\n\n### Example 1: Full Interview Loop Design\n\n**Input:**\n```\nDesign interview process for:\n- Role: Senior Software Engineer\n- Team: 5 engineers, 1 manager\n- Timeline: Hire within 3 weeks\n- Format: Hybrid (some remote, some onsite)\n```\n\n**Output:**\n```\n## Interview Process: Senior Software Engineer\n\n### Process Overview\n\n| Stage | Format | Duration | Interviewers | Turnaround |\n|-------|--------|----------|--------------|------------|\n| 1. Recruiter Screen | Phone | 30 min | Recruiter | Same day |\n| 2. Technical Screen | Video | 60 min | Engineer | 24 hours |\n| 3. Onsite Loop | In-person | 4 hours | Panel | 24 hours |\n| 4. Debrief | Internal | 30 min | All | Same day |\n| 5. Offer | Call | 15 min | HM + Recruiter | 48 hours |\n\n**Total Timeline:** 10-14 business days\n\n---\n\n### Stage 1: Recruiter Screen\n\n**Format:** Phone\u002FVideo call\n**Duration:** 30 minutes\n**Interviewer:** Recruiter\n\n**Purpose:** Basic qualification, logistics, motivation\n\n**Questions:**\n1. Walk me through your background (5 min)\n2. Why are you interested in this role? (3 min)\n3. What's your ideal next role? (3 min)\n4. Salary expectations? (2 min)\n5. Timeline and availability? (2 min)\n6. Candidate questions (10 min)\n\n**Pass Criteria:**\n- [ ] Meets minimum experience (5+ years)\n- [ ] Reasonable salary alignment\n- [ ] Available within timeline\n- [ ] Genuine interest\n\n---\n\n### Stage 2: Technical Screen\n\n**Format:** Video call with code sharing\n**Duration:** 60 minutes\n**Interviewer:** Senior Engineer (Sarah)\n\n**Purpose:** Technical depth, problem-solving, code quality\n\n**Structure:**\n- 5 min: Introductions\n- 10 min: Technical background discussion\n- 35 min: Coding problem (medium difficulty)\n- 10 min: System design discussion\n- 5 min: Candidate questions\n\n**Assessment Areas:**\n| Area | Weight | Signals |\n|------|--------|---------|\n| Problem solving | 40% | Approach, communication |\n| Code quality | 30% | Clean, tested, efficient |\n| Technical depth | 20% | Language mastery, patterns |\n| Collaboration | 10% | Receptive to hints, explains well |\n\n**Pass Criteria:** Score 3+ on each area (1-5 scale)\n\n---\n\n### Stage 3: Onsite Loop (4 Hours)\n\n**Panel Composition:**\n\n| Time | Interview | Interviewer | Focus |\n|------|-----------|-------------|-------|\n| 9:00 | System Design | Tom (Staff Eng) | Architecture thinking |\n| 10:00 | Code Review | Lisa (Senior Eng) | Code quality, feedback |\n| 11:00 | Hiring Manager | Mike (Eng Manager) | Fit, growth, expectations |\n| 12:00 | Lunch | Any team member | Culture, informal |\n| 1:00 | Behavioral | Sarah (Senior Eng) | STAR examples |\n\n**Detailed Interview Guides:**\n\n#### System Design (Tom, 9:00-10:00)\n\n**Question:** \"Design a real-time notification system for a social media platform\"\n\n**Assessment:**\n| Criterion | What to Look For |\n|-----------|------------------|\n| Requirements gathering | Clarifies scale, features |\n| High-level design | Components, data flow |\n| Deep dive | Storage, queuing, delivery |\n| Trade-offs | Articulates decisions |\n| Scale | Handles growth scenarios |\n\n#### Code Review (Lisa, 10:00-11:00)\n\n**Exercise:** Review prepared PR with intentional issues\n\n**Assessment:**\n| Criterion | What to Look For |\n|-----------|------------------|\n| Bug detection | Finds logic errors |\n| Style feedback | Constructive, specific |\n| Security awareness | Identifies vulnerabilities |\n| Communication | Kind, actionable feedback |\n\n#### Hiring Manager (Mike, 11:00-12:00)\n\n**Topics:**\n1. Career trajectory and goals\n2. Management style preferences\n3. Conflict resolution examples\n4. Growth areas and learning\n5. Questions about team\u002Frole\n\n#### Behavioral (Sarah, 1:00-2:00)\n\n**STAR Questions:**\n1. \"Tell me about a time you disagreed with a technical decision\"\n2. \"Describe a project that failed and what you learned\"\n3. \"Give an example of helping a teammate grow\"\n4. \"Tell me about navigating ambiguity\"\n\n---\n\n### Stage 4: Debrief\n\n**Timing:** Same day, 4:00 PM\n**Attendees:** All interviewers + Recruiter\n**Format:** 30-minute structured discussion\n\n**Agenda:**\n| Time | Activity |\n|------|----------|\n| 0-5 | Written feedback review (pre-submitted) |\n| 5-20 | Round-robin: Each interviewer shares (3 min each) |\n| 20-25 | Discussion of concerns\u002Fquestions |\n| 25-30 | Decision: Strong Yes \u002F Yes \u002F No \u002F Strong No |\n\n**Decision Criteria:**\n- Strong Yes from HM required\n- No more than 1 \"No\" vote\n- Technical interviewers must be Yes+\n\n---\n\n### Communication Templates\n\n**Interview Confirmation:**\n```\nSubject: Interview Confirmation - Senior Software Engineer\n\nHi [Name],\n\nWe're excited to have you visit for your onsite interviews!\n\nDate: [Date]\nTime: 9:00 AM - 2:00 PM\nLocation: [Address]\n\nYour schedule:\n9:00 - System Design with Tom\n10:00 - Code Review with Lisa\n11:00 - Hiring Manager with Mike\n12:00 - Lunch with the team\n1:00 - Behavioral with Sarah\n\nPlease bring a laptop and valid ID. Parking validation available.\n\nReply to confirm or if you have any questions.\n\nBest,\n[Recruiter]\n```\n\n**Post-Interview Next Steps:**\n```\nSubject: Thank You & Next Steps\n\nHi [Name],\n\nThank you for spending time with our team today!\n\nOur team will be debriefing this afternoon, and you'll hear\nfrom us within 48 hours on next steps.\n\nIn the meantime, please don't hesitate to reach out with\nany questions.\n\nBest,\n[Recruiter]\n```\n```\n\n### Example 2: Quick Schedule Coordination\n\n**Input:**\n```\nNeed to schedule 4 interviews for tomorrow:\n- Candidates: Alice, Bob, Carol\n- Interviewers available: Mike (9-12), Sarah (10-2), Tom (11-4)\n- Each interview: 45 minutes\n```\n\n**Output:**\n```\n## Optimized Interview Schedule\n\n### Tomorrow's Schedule\n\n| Time | Mike | Sarah | Tom |\n|------|------|-------|-----|\n| 9:00 | Alice | - | - |\n| 10:00 | - | Bob | - |\n| 11:00 | Carol | - | Alice |\n| 12:00 | - | Carol | Bob |\n| 1:00 | - | - | Carol |\n\n### By Candidate\n\n| Candidate | Interview 1 | Interview 2 |\n|-----------|-------------|-------------|\n| Alice | Mike @ 9:00 | Tom @ 11:00 |\n| Bob | Sarah @ 10:00 | Tom @ 12:00 |\n| Carol | Mike @ 11:00 | Sarah @ 12:00 |\n\n### Notes\n\n- Alice: 2-hour gap between interviews (offer coffee\u002Fworkspace)\n- Bob: Back-to-back, efficient\n- Carol: Back-to-back, efficient\n\n### Calendar Invites Needed\n\n1. Alice + Mike: 9:00-9:45\n2. Bob + Sarah: 10:00-10:45\n3. Alice + Tom: 11:00-11:45\n4. Carol + Mike: 11:00-11:45\n5. Bob + Tom: 12:00-12:45\n6. Carol + Sarah: 12:00-12:45\n7. Carol + Tom: 1:00-1:45\n```\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Designing interview stages\n- Optimizing panel composition\n- Creating schedules\n- Drafting communications\n\n### What This Skill Cannot Do\n- Access actual calendars\n- Send invitations\n- Know interviewer preferences\n- Make hiring decisions\n\n## Iteration Guide\n\n**Follow-up Prompts:**\n- \"Create interview questions for [stage]\"\n- \"Draft the candidate rejection email\"\n- \"How should we handle scheduling conflict with [interviewer]?\"\n- \"Design a scorecard for [interview type]\"\n\n## References\n\n- Google re:Work Hiring Practices\n- Lever Interview Scheduling Guide\n- SHRM Interview Best Practices\n- Greenhouse Structured Interviewing\n\n## Related Skills\n\n- `resume-screener` - Pre-interview evaluation\n- `onboarding-guide` - Post-hire process\n- `employee-support` - New hire support\n\n## Skill Metadata\n\n- **Domain**: HR Operations\n- **Complexity**: Intermediate\n- **Mode**: cyborg\n- **Time to Value**: 30-60 min per role\n- **Prerequisites**: Role requirements, panel availability\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25,"mcp-server":26},"ClawFu","1.0.0","@clawfu\u002Fmcp-skills","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Finterview-scheduler",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add roohe\u002Fagentic-super-skills --skill interview-scheduler",{"tool":41,"command":42},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill interview-scheduler",{"tool":44,"command":45},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill interview-scheduler","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Finterview-scheduler\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]