# Recruit

Use when the user wants candidates for a role; they paste a LinkedIn job post (or a job...

- Repository: https://github.com/superdesigndev/treg (6950 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add superdesigndev/treg --skill recruit -g -a claude-code -y`
Codex: `npx skills add superdesigndev/treg --skill recruit -g -a codex -y`
Cursor: `npx skills add superdesigndev/treg --skill recruit -g -a cursor -y`
Gemini CLI: `npx skills add superdesigndev/treg --skill recruit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add superdesigndev/treg`

## Description

Use when the user wants candidates for a role; they paste a LinkedIn job post (or a job description) and want the people who fit it, ranked, with a reason for each and a personal email and phone to reach them. Also for "source candidates", "find people for this job", "build a shortlist", or turning a job post into a contactable candidate list.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Recruit

A job post in, a ranked shortlist out: people who fit, one line on why, and a way to reach them.
Every stage is counted and every contact lookup leaves a vendor trail, written to a run file.

Runs on treg, through its MCP tools or the `treg` CLI; either is enough. Over MCP, each command
below maps onto a tool: `treg catalog search` is `catalog_search`, `treg catalog get` is
`catalog_get`, `treg call` is `call`. With neither, treg is not set up: https://treg.to/llms.txt says how.
Install only if the human asked you to; otherwise tell them how and stop.

## The run

1. **Read the job.** `treg catalog search "linkedin job details"`, then call the best row with the
   post URL. No post URL: use the text the user pasted.
2. **Extract criteria** from the post, yourself: title variants (the title as posted plus two to
   four names the same job goes by), must-have skills, seniority, locations (and whether remote is
   fine), and the hiring company, which is always excluded. Show the criteria to the user in five
   lines before spending; adjust if they object.
3. **Search** with the routed people search, one call per title variant (and per location when there
   are several):

   ```
   treg call treg.people.search --data '{"title":"Staff Backend Engineer","location":"Berlin, Germany","country":"DE","keywords":["go","kafka"],"limit":25}'
   ```

The rest: https://github.com/superdesigndev/treg/blob/HEAD/plugins/workflows/recruit/skills/recruit/SKILL.md