SkillFoxx

Recruiting Co-Pilot skill

YC skills for Claude Code hiring: pipeline, candidate emails, scheduling, Work at a Startup, Ashby and Gmail

  • 125 ★ on the repository
  • Last commit
Skill

Broad access

Why this level

  • Works with Gmail, a calendar and hiring systems: reads correspondence and prepares emails and invites.
  • Candidate data passes through MCP servers and the model.
All reasons and checks

yc-software/recruitingAuthor:yc-software

Install

Manual install

git clone https://github.com/yc-software/recruiting.git

Install step 4: after cloning, run `claude` from the repository root.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Works with Gmail, a calendar and hiring systems: reads correspondence and prepares emails and invites.
  • Candidate data passes through MCP servers and the model.

This is third-party code. Review the repository files before installing.

What it does

Recruiting Co-Pilot runs the whole hiring loop through Claude Code in natural language. The skills in `.claude/skills/` build a pipeline by stage with urgency tiers, write personalized candidate emails and follow-ups, find calendar slots and send Zoom or in-person invites, triage the inbox, cross-reference candidate data across WAAS, Ashby, Gmail and calendar, clean up mail and review new applicants. Integration goes through MCP servers: `waas-mcp` for Work at a Startup and `mcp-ashby` for the Ashby ATS, while Gmail and Google Calendar use Claude's built-in integrations. Evaluation criteria live in a job file such as `product-engineer.md`. For rejections the skill drafts emails calibrated to the pipeline stage. The authors stress that the tool does not replace a founder's judgment and is not meant for spam.

Who it is for. Startup founders and hiring managers who recruit through Work at a Startup and Ashby and want less routine.

Good fit when

  • Mornings call for one overview: mail, the ATS pipeline, WAAS applicants and the calendar.
  • A candidate proposed a time in an email and the calendar must be checked and a reply sent.
  • New applicants are rated against your job criteria file.
  • Rejections are written personally and tuned to the pipeline stage.

Not a fit when

  • You do not use Work at a Startup or Ashby: the integration is built around them.
  • You want mass cold outreach.
  • Sending emails without your review is unacceptable.

Example request

triage: show what needs attention today across mail, the ATS and Work at a Startup.

Limitations

The skills handle real correspondence, a calendar and a hiring system, so review email and invite drafts before sending. Claude Code, the `waas-mcp` and `mcp-ashby` MCP servers (installed through `uv tool install git+...`) and three files from `.example` templates are needed: `user.md`, `ashby.md` and a job file. These files are gitignored and stay local. The repository has no stated license. The authors advise against using the set to spam candidates and say that does not work.

How to disable. Delete the cloned repository and the MCP servers with `uv tool uninstall`. Revoke Gmail and Calendar access in Claude's integration settings.

FAQ

How do I install Recruiting Co-Pilot?

Run `git clone https://github.com/yc-software/recruiting.git`, enter the folder and run `claude`. Skills in `.claude/skills/` are picked up automatically.

Which MCP servers are needed?

`uv tool install git+https://github.com/yc-software/waas-mcp` for Work at a Startup and `uv tool install git+https://github.com/ryankicks/mcp-ashby` for Ashby. Gmail and Calendar use Claude's built-in integrations.

Can only WAAS or only Ashby be used?

Yes, either system alone or both together. The YC team uses both.

How do I update an MCP server?

Run `uv tool install git+https://github.com/yc-software/waas-mcp --force` after a new version is released.

What goes into the configs?

User details, Ashby identifiers and a job description with criteria such as `product-engineer.md`.

Discussion

No questions or reviews yet.

Skills
Needs a VPN

A Claude Code workspace that tracks jobs, finds roles and sends first messages to 1st-degree LinkedIn connections

PluginBroad access237

AI Sales Team

AI Sales Team for Claude Code

A set of Claude Code skills and agents: research companies, qualify leads with BANT and MEDDIC, find decision makers, draft outreach and pipeline reports

SkillExtended access1.5K

Two LinkedIn skills via Linked API: people and company search, messages, posts and a lead pipeline with connection invites.

SkillBroad access110

A Codex skill that finds potential first customers from public demand signals, verifies an open contact route and builds a report.

SkillExtended access1.3K

Six Claude Code and Cowork plugins with 81 skills for customer success: QBR, renewals, onboarding and forecasting

PluginExtended access70
Russian stack

A skill that connects two Avito MCP servers: the official API for your own account and public search for competitor research

SkillExtended access

README in short

The skill set is built from practices YC uses when helping companies. The docs include real session examples: morning triage, interview scheduling and bulk applicant review.

README badge

Original SKILL.md

---
name: candidate-brief
description: |
  Generate a quick one-paragraph brief on a candidate by pulling from all available sources.
  Replaces opening LinkedIn, Ashby, and email tabs. Use when the user asks "who is this person",
  "tell me about X", "brief me on X", or is triaging candidates and needs context fast.
allowed-tools:
  - Bash
  - Read
  - mcp__ashby__candidate_search
  - mcp__ashby__candidate_info
  - mcp__ashby__application_info
  - mcp__ashby__candidate_list_notes
  - mcp__google-workspace__gmail_query_emails
  - mcp__google-workspace__gmail_get_email
  - mcp__waas__candidate_show
  - mcp__waas__candidate_status_show
  - mcp__waas__candidate_notes_list
---

> **Note:** Read `recruit-config/user.md` for the hiring manager's name, email, and preferences. Do not hardcode any user-specific values.


# Candidate Brief

Generate a quick contextual brief on a candidate so the hiring manager can recall and calibrate without opening 5 tabs.

## Unified Resolver

Read `recruit-config/resolve-candidate.md` for the shared procedure to pull data from all 4 sources (WAAS MCP, Ashby, Gmail, Calendar). Use the WAAS data (positions, educations, role, experience) for richer background info than Ashby alone provides.

## Input

One or more candidate names:
- `/candidate-brief Jane Doe`
- `/candidate-brief John Smith, Candidate C`

## Procedure

For each candidate, pull from ALL sources in parallel:

### 1. Ashby profile
```
candidate_search(name) → position, company, school, socialLinks (LinkedIn), customFields (YC Bio Summary)
```

### 2. Ashby application
```
application_info(applicationId) → source, currentInterviewStage, applicationHistory (how long in each stage)
```

Report a problem