Your agent can embellish.
Teach it to screen.

One install gives your agent 13 job-search commands, every finding run through 5 recruiter filters: speed, relevance, evidence, risk, clarity. What it reads is what a screener would see.

13 commands 5 recruiter filters ~2,500 lines of instruction 0 API keys

for coding agents · free, open, no auth

install

Copy one line. Get screened first.

Detects Claude Code, Cursor, Codex, Qoder and more, then writes the skill into the right folder. Add --dry-run to see the plan first.

npx skills add arm-pz/recruiter-lens

the full vocabulary

13 commands, 5 filters.

Or skip the commands. Ask "why would this resume get rejected?" in plain language and the skill routes it, naming the command it picked.

Analysis 5

See the material the way the screener does.

  • scan
  • critique
  • ats-check
  • reject-reasons
  • linkedin-audit

Preparation 4

Walk in already knowing what they'll ask.

  • predict-questions
  • gap-analysis
  • tailor
  • ai-guidelines

Optimization 4

Better presentation of real experience, never misrepresentation.

  • format-fix
  • keyword-match
  • impact-boost
  • red-flag-review

house rules

What the lens never does.

Invent nothing

Numbers, titles, employers and dates come from the candidate. A missing metric gets a question or a visible [metric: ?], never a guess.

Tend, not rule

Screening behavior is reported tendency, not insider knowledge. Region, industry and seniority change what applies, and the skill says when.

Stay honest

No claim that would collapse under interview follow-up. Gaps and career changes get a brief, honest context line, never concealment.

Know what they see in the first six seconds.

Free, open, and it runs entirely inside the agent you already use.

Install recruiter-lens Read the source