When should you use it?
- You are actively looking for work
- You want fewer, better applications
- Level and pay matter as much as title
Not for: Auto-applying to everything; Sites whose terms forbid automated browsing
What do you need, and what do you get?
You need
- Resume
- Desired seniority and minimum salary
- Saved search criteria
You get
- Daily shortlist with fit notes
- Level and pay context per role
How does it work, step by step?
- Set the searchDefine titles, locations and seniority you want.
- Add pay contextHave the agent look up typical level and compensation for each company.
- Score fitCompare each posting to your resume and explain the match.
- Cut to a shortlistReturn only roles above your thresholds.
- Judge yourselfRead each and decide; apply with tailored material.
The prompt
Our own prompt, inspired by malfist on Hacker News and written to work in ChatGPT agent, Claude, Grok Bot and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Each morning, review new postings matching {search}. For each, look up typical level and pay for that company, compare to my floor {pay_floor}, and score match with my resume {resume} on a five-point scale, giving two reasons. Return only strong matches that clear the floor, as a table with links. Do not apply.
Inspired by malfist on Hacker News: Hacker News comment on running a targeted job search after a layoff. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Public pay data is self-reported; treat it as a range.
- Mass applying defeats the purpose; keep the human cut.
Our take
The value is focus. Daily screening that combines fit and pay context produces a short list worth tailoring for, and a targeted pipeline fills up fast. Keep the human cut sacred: the agent proposes, you choose. Review the skip list weekly so good roles are not filtered out forever. malfist's morning run narrows LinkedIn to roughly five to ten posts by combining seniority and pay context from levels.fyi with a fit score against his resume. Define titles, locations and level up front, and ask the agent to explain each match rather than give a bare number. Self-reported pay data is a range, not a promise, so treat it that way. Mass applying would defeat the purpose; tailor material for the shortlist instead. Review the skipped roles now and then, since a threshold set too tight can hide a good opening for weeks. The agent proposes; you choose and you apply. Check that the sites you scan allow automated browsing, and never let it apply on your behalf.
Where the time goes back: The morning scan, the pay lookup and the first fit check are done before you sit down.
FAQ
How many roles does it surface?
Does it apply for me?
Source and credit
Inspired by malfist on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on running a targeted job search after a layoff
- Creator
- malfist on Hacker News
- Published on
- Hacker News
- Original date
- Oct 9, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.