Screen new applicants against your must-haves
Each new applicant checked against the job's must-haves, with evidence from the resume. You decide.
- On a schedule: Every weekday at 8:00
What it does
The task
Open the job job in Ashby and read the applicants who applied since the last run. Check each resume and the application answers against these must-haves: must haves. Use only job-related facts, and ignore the name, age, gender, photo, nationality and other personal traits. For each applicant, write met, not met or unclear for each must-have, with a short quote as evidence. Send me a table, the applicants who meet all must-haves first. Do not move, reject or contact any candidate.
- It works in Ashby, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- As a routine it runs every weekday at 8:00 (cron
0 8 * * 1-5).
What you give it
| Blank | What to give | Example |
|---|---|---|
| job | The job in Ashby | Senior Backend Engineer, Payments |
| must haves | The must-haves, separated by commas | 5 years of Go or Java, payment or ledger systems, SQL |
What you get back
An example run with the example values above. Your run uses your own data.
Senior Backend Engineer, Payments: 18 new applicants
| Applicant | Go or Java, 5 years | Payments | SQL | Evidence |
|---|---|---|---|---|
| A. Kowalski | Met | Met | Met | "7 years of Go, built the ledger at Fintrail" |
| R. Mensah | Met | Unclear | Met | "Checkout team, 2 years", no detail on payment systems |
| L. Fischer | Not met (3 years) | Met | Met | "Java since 2023" |
... 15 more
All must-haves met: 4. Unclear: 6. Not met: 8.
No candidate was moved or contacted.
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in 2 blanks
Type job and must haves. Tab moves to the next blank.
- 03
Run it, then repeat it
Run sends it once. To run it every weekday at 8:00, make a routine on cuiar.com/routines or with the CLI below.
As a routine, from the terminal
cuiar routines create "Screen new applicants against your must-haves" --schedule "0 8 * * 1-5" --time-zone Europe/Berlin \
"Open the job Senior Backend Engineer, Payments in Ashby and read the applicants who applied since the last run. Check each resume and the application answers against these must-haves: 5 years of Go or Java, payment or ledger systems, SQL. Use only job-related facts, and ignore the name, age, gender, photo, nationality and other personal traits. For each applicant, write met, not met or unclear for each must-have, with a short quote as evidence. Send me a table, the applicants who meet all must-haves first. Do not move, reject or contact any candidate."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool create_routine to run my "Screen new applicants against your must-haves" template with job = Senior Backend Engineer, Payments; must haves = 5 years of Go or Java, payment or ledger systems, SQL.Setup for other agents: AI agents.
The tool call
{
"name": "create_routine",
"arguments": {
"name": "Screen new applicants against your must-haves",
"task": "Open the job Senior Backend Engineer, Payments in Ashby and read the applicants who applied since the last run. Check each resume and the application answers against these must-haves: 5 years of Go or Java, payment or ledger systems, SQL. Use only job-related facts, and ignore the name, age, gender, photo, nationality and other personal traits. For each applicant, write met, not met or unclear for each must-have, with a short quote as evidence. Send me a table, the applicants who meet all must-haves first. Do not move, reject or contact any candidate.",
"schedule": "0 8 * * 1-5",
"time_zone": "Europe/Berlin"
}
}Related templates
All recruiting templatesRecruitingAsks first
Prepare an offer letter and send it for signature
Your offer template filled with the approved terms and sent for e-signature after you approve it.
You start it: When you start it- AAshby
- Google Docs
- DDocuSign
RecruitingAsks first
Remind interviewers to submit their feedback
Interviews with no feedback after your deadline, with a short reminder to each interviewer.
On a schedule: Every weekday at 11:00- LLever
- SSlack
Recruiting
Send a weekly hiring pipeline report
Candidates per stage for each open job, new applicants, offers and stuck candidates, in one table.
On a schedule: Every Monday at 8:30- Greenhouse
- Google Sheets
RecruitingAsks first
Update candidates who are waiting for news
A short update or a kind decline for each candidate with no news for a week. You approve each e-mail.
On a schedule: Every Thursday at 15:00- WWorkable
- Gmail
RecruitingAsks first
Write a job post and publish it on job boards
A clear post with the pay, duties and must-haves, created in your ATS and published after you approve it.
You start it: When you start it- Greenhouse
- LLinkedIn
- Indeed
Recruiting
Check your job posts against pay transparency laws
Each live post checked against the pay transparency rules of its location, with the fix for each gap.
You start it: When you start it- Any job board
- Any government site