Pace
← All cookbooks People cookbook

People

Recruiting pipeline status. Interview prep that matches the role. Onboarding day-one without the checklist scramble.

Marquee recipe

Weekly recruiting pipeline digest

Hiring managers know where every open req stands without asking.

Trigger
Routine, schedule, weekly Monday 08:00
Skills
recruiting-pipeline, people-report
Features
Routines (cloud schedule), ATS connector, Slack delivery

Hiring managers walk into Monday standup already knowing where every open req stands : candidates aging in a stage, interviews scheduled for the week, offers extended, declines. No more "where are we with X" updates.

How to set it up

  1. 1
    Install the human-resources plugin
    Install in Cowork ↗ claude plugin install human-resources@pace
  2. 2
    Authorize your ATS + Slack

    Most ATSes (Ashby, Greenhouse, Lever, and others) don't have first-party MCP servers yet. The skill still works against pasted exports, structured docs in Notion, or via the Custom URL pattern in the connector docs. If you want us to set this up against your specific ATS, talk to us.

  3. 3
    Create the scheduled routine

    In Cowork, open Routines → New routine → Schedule · Weekly · Monday · 08:00.

  4. 4
    Paste this as the routine prompt
    Routine prompt 
    Run recruiting-pipeline against the
ATS. For each open requisition, surface:

  - Stage of every active candidate
  - Time-in-stage (flag anyone > 10 business days)
  - Interviews scheduled this week (panel + candidate names)
  - Offers extended / accepted / declined since last week
  - Reqs without any candidates in pipeline ("stuck")

Format as a digest grouped by hiring manager. Post to
#hiring-weekly in Slack. Tag each hiring manager next
to their reqs so they get a heads-up DM.
  5. 5
    Click Run now to verify

    Eyeball the first digest for accuracy (does aging match what you see in the ATS?). Once you trust it, Mondays at 08:00 are automatic.

Interview prep tailored to the role and the candidate

Trigger
Routine, API trigger fired by your calendar webhook (filter on "interview")
Skills
interview-prep
Features
Routines (API trigger), ATS + Apollo connectors, plan mode

When an interview lands on the calendar, interview-prep pulls the JD, candidate resume, and prior round feedback. It drops a prep brief into the event description: focus areas, suggested probing questions, and what to avoid re-asking. Panel walks in calibrated.

1:1 prep brief, in the manager's inbox 30 minutes before the meeting

Before every 1:1, a routine assembles a brief: what the direct has shipped (Linear, GitHub), what they've blocked on (Slack threads, open PRs), what came up in the last 1:1 notes. Manager walks into the meeting with the picture instead of asking "so what have you been up to?".

Trigger
Routine, calendar webhook 30 min before any 1:1 event
Skills
onboarding-plan, review-feedback
Features
Routines (calendar webhook), Linear + GitHub + Slack + Notion connectors

How to set it up

  1. 1
    Create the API-triggered routine

    In Cowork, open Routines → New routine → API. Save and copy the routine URL + bearer token; point the upstream webhook at it (e.g. calendar provider, Intercom webhook, PagerDuty webhook, depending on the trigger).

  2. 2
    Paste this as the routine prompt
    1:1 prep prompt 
    30 minutes before any 1:1 on my calendar, assemble a brief on the direct I'm meeting with:

- What they shipped this week (Linear closed, GitHub merged).
- What they're stuck on (open PRs over 3 days old, Slack threads where they pinged me, blocked Linear tickets).
- What came up in our last 1:1 notes in Notion.

Drop the brief into the calendar event description so I see it when I open the meeting.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.

Offer letter drafted from the candidate record

Hiring manager clicks "send offer" in the ATS. A routine pulls the candidate's role, level, band, and recruiter notes, then drafts the offer letter from your standard template with the right compensation, equity grant, and start-date language. People ops reviews and sends. 40 minutes per offer becomes 5.

Trigger
Routine, API trigger fired by ATS stage-change to "offer"
Skills
job-description, comp-analysis
Features
Routines (API trigger), ATS data (via Notion exports or Custom URL), plan mode for people-ops review

How to set it up

  1. 1
    Create the API-triggered routine

    In Cowork, open Routines → New routine → API. Save and copy the routine URL + bearer token; point the upstream webhook at it (e.g. calendar provider, Intercom webhook, PagerDuty webhook, depending on the trigger).

  2. 2
    Paste this as the routine prompt
    Offer letter prompt 
    When a candidate hits the "offer" stage in our ATS, pull their record: role, level, band, recruiter notes, start date. Draft the offer letter from our standard template with the right comp (base + variable), equity grant per the band, and start-date language.

Park the draft in plan mode for people-ops to review. Once approved, the recruiter sends from the ATS.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.