Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,11 @@
"source": "./customer-support",
"description": "Triage tickets, draft responses, escalate issues, and build your knowledge base. Research customer context and turn resolved issues into self-service content."
},
{
"name": "recruiting",
"source": "./recruiting",
"description": "Screen resumes, write job descriptions, source candidates, build interview kits, run debriefs, and manage your hiring pipeline. Works standalone or supercharged with ATS, email, and calendar integrations."
},
{
"name": "product-management",
"source": "./product-management",
Expand Down
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,14 @@ Each plugin bundles the skills, connectors, slash commands, and sub-agents for a

## Plugin Marketplace

We're open-sourcing 11 plugins built and inspired by our own work:
We're open-sourcing 12 plugins built and inspired by our own work:

| Plugin | How it helps | Connectors |
|--------|-------------|------------|
| **[productivity](./productivity)** | Manage tasks, calendars, daily workflows, and personal context so you spend less time repeating yourself. | Slack, Notion, Asana, Linear, Jira, Monday, ClickUp, Microsoft 365 |
| **[sales](./sales)** | Research prospects, prep for calls, review your pipeline, draft outreach, and build competitive battlecards. | Slack, HubSpot, Close, Clay, ZoomInfo, Notion, Jira, Fireflies, Microsoft 365 |
| **[customer-support](./customer-support)** | Triage tickets, draft responses, package escalations, research customer context, and turn resolved issues into knowledge base articles. | Slack, Intercom, HubSpot, Guru, Jira, Notion, Microsoft 365 |
| **[recruiting](./recruiting)** | Screen resumes, source candidates, design interviews, run debriefs, write job descriptions, and manage your hiring pipeline. | Slack, Greenhouse, Lever, Apollo, Clay, LinkedIn, Notion, Zoom, Google Calendar, Gmail |
| **[product-management](./product-management)** | Write specs, plan roadmaps, synthesize user research, keep stakeholders updated, and track the competitive landscape. | Slack, Linear, Asana, Monday, ClickUp, Jira, Notion, Figma, Amplitude, Pendo, Intercom, Fireflies |
| **[marketing](./marketing)** | Draft content, plan campaigns, enforce brand voice, brief on competitors, and report on performance across channels. | Slack, Canva, Figma, HubSpot, Amplitude, Notion, Ahrefs, SimilarWeb, Klaviyo |
| **[legal](./legal)** | Review contracts, triage NDAs, navigate compliance, assess risk, prep for meetings, and draft templated responses. | Slack, Box, Egnyte, Jira, Microsoft 365 |
Expand Down
9 changes: 9 additions & 0 deletions recruiting/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"name": "recruiting",
"version": "1.0.0",
"description": "Screen resumes, write job descriptions, source candidates, build interview kits, run debriefs, and manage your hiring pipeline. Built for talent acquisition professionals, HR generalists, and startup founders making their first hires.",
"author": {
"name": "Jeff Otterson",
"url": "https://meritforgeai.com"
}
}
52 changes: 52 additions & 0 deletions recruiting/.mcp.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
{
"mcpServers": {
"slack": {
"type": "http",
"url": "https://mcp.slack.com/mcp"
},
"google-calendar": {
"type": "http",
"url": "https://gcal.mcp.claude.com/mcp"
},
"gmail": {
"type": "http",
"url": "https://gmail.mcp.claude.com/mcp"
},
"ms365": {
"type": "http",
"url": "https://microsoft365.mcp.claude.com/mcp"
},
"notion": {
"type": "http",
"url": "https://mcp.notion.com/mcp"
},
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v1/mcp"
},
"greenhouse": {
"type": "http",
"url": "https://mcp.greenhouse.io/mcp"
},
"lever": {
"type": "http",
"url": "https://mcp.lever.co/mcp"
},
"apollo": {
"type": "http",
"url": "https://api.apollo.io/mcp"
},
"linkedin": {
"type": "http",
"url": "https://mcp.linkedin.com/mcp"
},
"clay": {
"type": "http",
"url": "https://api.clay.com/v3/mcp"
},
"zoom": {
"type": "http",
"url": "https://mcp.zoom.us/mcp"
}
}
}
22 changes: 22 additions & 0 deletions recruiting/CONNECTORS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Connectors

## How tool references work

Plugin files use `~~category` as a placeholder for whatever tool the user connects in that category. For example, `~~ATS` might mean Greenhouse, Lever, Ashby, or any other applicant tracking system with an MCP server.

Plugins are **tool-agnostic** β€” they describe workflows in terms of categories (ATS, email, calendar, etc.) rather than specific products. The `.mcp.json` pre-configures specific MCP servers, but any MCP server in that category works.

## Connectors for this plugin

| Category | Placeholder | Included servers | Other options |
|----------|-------------|-----------------|---------------|
| ATS | `~~ATS` | Greenhouse, Lever | Ashby, Workday Recruiting, iCIMS, Jobvite, SmartRecruiters |
| Calendar | `~~calendar` | Google Calendar, Microsoft 365 | Calendly |
| Chat | `~~chat` | Slack | Microsoft Teams, Discord |
| Cloud storage | `~~cloud storage` | β€” | Google Drive, Dropbox, SharePoint |
| CRM | `~~CRM` | β€” | HubSpot, Salesforce, Bullhorn |
| Data enrichment | `~~data enrichment` | Apollo, Clay, LinkedIn | Clearbit, ZoomInfo, Lusha, People Data Labs |
| Email | `~~email` | Gmail, Microsoft 365 | β€” |
| HRIS | `~~HRIS` | β€” | BambooHR, Workday, Rippling, Gusto |
| Knowledge base | `~~knowledge base` | Notion, Atlassian (Confluence) | Guru, Slite, Coda |
| Video conferencing | `~~video` | Zoom | Google Meet, Microsoft Teams |
143 changes: 143 additions & 0 deletions recruiting/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,143 @@
# Recruiting Plugin

A recruiting and talent acquisition plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application β€” though it also works in Claude Code. Source candidates, screen resumes, design interviews, run debriefs, write job descriptions, and manage your hiring pipeline. Works with any recruiting team β€” standalone with web search and your input, supercharged when you connect your ATS, email, and other tools.

## Installation

```bash
claude plugins add knowledge-work-plugins/recruiting
```

## Commands

Explicit workflows you invoke with a slash command:

| Command | Description |
|---|---|
| `/source` | Build a targeted sourcing strategy β€” channels, Boolean strings, outreach angles |
| `/screen` | Screen a candidate against job requirements β€” fit matrix, signals, and recommendation |
| `/interview-prep` | Generate interview questions, scorecards, and loop structure for a role |
| `/debrief` | Synthesize interview feedback into a structured hiring recommendation |
| `/pipeline-review` | Analyze pipeline health β€” conversion rates, bottlenecks, and action plan |
| `/write-jd` | Write or improve a job description with inclusive language and clear requirements |
| `/outreach` | Draft personalized candidate outreach messages with research-backed hooks |
| `/offer-prep` | Prepare and analyze a compensation offer with market benchmarks |

All commands work **standalone** (paste resumes, JDs, notes, or describe your situation) and get **supercharged** with MCP connectors.

## Skills

Domain knowledge Claude uses automatically when relevant:

| Skill | Description |
|---|---|
| `candidate-evaluation` | Structured rubrics and scorecards for consistent, evidence-based assessment with bias mitigation |
| `interview-design` | Build interview loops with competency coverage mapping and format selection |
| `job-architecture` | Leveling frameworks, competency models, and role scoping across functions |
| `market-intelligence` | Talent market conditions, compensation benchmarks, and competitor intel |
| `pipeline-analytics` | Funnel metrics, conversion rates, time-to-fill analysis, and bottleneck diagnosis |
| `sourcing-strategy` | Boolean strings, channel mix optimization, and passive candidate engagement |
| `diversity-recruiting` | Inclusive hiring practices, bias mitigation, and diverse sourcing strategies |
| `employer-branding` | EVP messaging, job marketing, and candidate experience optimization |

## Example Workflows

### Writing a Job Description

```
/write-jd
```

Describe the role you're hiring for. Get a polished job description with clear requirements, inclusive language, and a compelling pitch. If your knowledge base is connected, it pulls your company's JD template and values.

### Screening a Candidate

```
/screen
```

Paste a resume and job description. Get a structured fit matrix scoring every dimension, strong signals, gaps, recruiter screen questions, and a clear advance/hold/pass recommendation.

### Building a Sourcing Plan

```
/source
```

Describe the role and target profile. Get a multi-channel sourcing strategy with Boolean search strings, outreach templates, and channel prioritization based on the talent market.

### Running a Debrief

```
/debrief
```

Paste interview feedback from your panel. Get a synthesized recommendation with dimension-by-dimension analysis, consensus view, and a clear hire/no-hire recommendation with reasoning.

### Researching the Market

Just ask naturally:
```
What's the market rate for a senior backend engineer in Austin?
```

The `market-intelligence` skill triggers automatically and gives you compensation benchmarks, talent supply data, and competitive landscape.

### Improving Your Pipeline

```
/pipeline-review
```

Paste pipeline data or describe your funnel. Get conversion rates benchmarked against industry standards, bottleneck diagnosis, and a prioritized action plan.

## Standalone + Supercharged

Every command and skill works without any integrations:

| What You Can Do | Standalone | Supercharged With |
|-----------------|------------|-------------------|
| Screen candidates | Paste resume + JD | ATS MCP (e.g. Greenhouse, Lever) |
| Write job descriptions | Describe the role | Knowledge base MCP (templates, values) |
| Build sourcing plans | Describe target profile | Enrichment MCP (e.g. Apollo, Clay) |
| Design interviews | Describe role + competencies | Knowledge base MCP (rubrics, guides) |
| Run debriefs | Paste interview feedback | ATS MCP (scorecards, history) |
| Draft outreach | Web search + your context | Email, Enrichment MCPs |
| Analyze pipeline | Paste data or describe funnel | ATS MCP (live pipeline data) |
| Prep offers | Describe role + candidate | HRIS MCP (comp bands, approvals) |

## MCP Integrations

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).

Connect your tools for a richer experience:

| Category | Examples | What It Enables |
|---|---|---|
| **ATS** | Greenhouse, Lever | Live candidate pipelines, stage updates, scorecards, duplicate detection |
| **Enrichment** | Apollo, Clay, LinkedIn | Candidate profile enrichment, contact info, company research |
| **Chat** | Slack, Teams | Hiring channel updates, hiring manager notifications, scorecard sharing |
| **Calendar** | Google Calendar, Microsoft 365 | Interviewer availability, loop scheduling, invite management |
| **Email** | Gmail, Microsoft 365 | Candidate outreach, follow-ups, offer letters |

See [CONNECTORS.md](CONNECTORS.md) for the full list of supported integrations, including HRIS, knowledge base, and video conferencing options.

## Settings

Create a local settings file at `recruiting/.claude/settings.local.json` to personalize:

```json
{
"company": "Your Company",
"industry": "Your Industry",
"team_size": "Approximate headcount",
"hiring_bar": "Key attributes your company values",
"interview_process": "Your standard interview loop structure",
"tools": {
"ats": "Greenhouse",
"hris": "Workday"
}
}
```

The plugin will ask you for this information interactively if it's not configured.
82 changes: 82 additions & 0 deletions recruiting/commands/debrief.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
---
description: Synthesize interview feedback into a hiring recommendation
argument-hint: "<candidate name or interview notes>"
---

# Interview Debrief

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md).

Synthesize feedback from multiple interviewers into a structured hiring recommendation. Surfaces consensus, disagreements, and evidence gaps to drive a productive debrief conversation.

## Input

The user provides one or more of:
- Individual interviewer scorecards or notes (pasted, uploaded, or described)
- Candidate name and role
- Interview panel composition
- Any known concerns or highlights from the hiring manager

If no feedback is provided, ask: "Share the interview feedback β€” paste scorecards, notes from each interviewer, or describe the signals from the panel."

## Workflow

1. **Collect feedback** β€” Parse all interviewer input, attributing each signal to its source
2. **Map to competencies** β€” Organize feedback by the competencies being evaluated, not by interviewer
3. **Identify consensus** β€” Flag areas where all interviewers agree (both positive and negative)
4. **Surface disagreements** β€” Highlight competencies where interviewers diverge, with each side's evidence
5. **Find evidence gaps** β€” Note competencies that were insufficiently tested or have conflicting signals
6. **Assess against the bar** β€” Compare the composite signal against the role's hiring bar
7. **Generate recommendation** β€” Produce a clear recommendation with confidence level
8. **Prepare debrief agenda** β€” Structure the debrief discussion to focus on disagreements and gaps first

## Output Structure

```
## Debrief Summary: [Candidate Name] β†’ [Role Title]

### Panel
| Interviewer | Stage | Overall rating |
|-------------|-------|---------------|
| [Name] | [Stage] | [Rating] |
| ... | ... | ... |

### Competency Heatmap

| Competency | [Interviewer 1] | [Interviewer 2] | [Interviewer 3] | Consensus |
|------------|----------------|----------------|----------------|-----------|
| [Comp 1] | βœ… Strong | βœ… Positive | ⚠️ Mixed | Positive |
| [Comp 2] | ❌ Concern | ⚠️ Mixed | ❌ Concern | Concern |
| ... | ... | ... | ... | ... |

### Areas of Consensus
**Strengths**: [What everyone agrees is strong, with evidence]
**Concerns**: [What everyone agrees is a gap, with evidence]

### Areas of Disagreement
**[Competency]**: [Interviewer A] saw [X signal] while [Interviewer B] saw [Y signal]. This likely reflects [possible explanation]. **Discuss in debrief.**

### Evidence Gaps
- [Competency not adequately tested β€” suggest follow-up]

### Recommendation: [Strong Hire / Hire / No Hire / Strong No Hire]
**Confidence**: [High / Medium / Low]
**Reasoning**: [2-3 sentences synthesizing the overall signal]

### Debrief Discussion Guide
1. **Start with**: [Key disagreement to resolve]
2. **Then discuss**: [Evidence gap to address]
3. **Decision point**: [What would move this from X to Y?]
```

## With Connectors

- **If ATS connected**: Pull submitted scorecards directly, update candidate disposition after the debrief
- **If chat connected**: Post the debrief summary to the hiring channel, notify the hiring manager
- **If calendar connected**: Check the scheduled debrief time and attendees

## Tips

- Best results when you have written feedback from every interviewer in the loop
- Include the role's leveling expectations if the decision hinges on "is this a senior or staff?"
- Flag if any interviewer has a known bias toward certain backgrounds or styles
Loading