Screen resumes against an approved job rubric, citing evidence and leaving human advance or reject decisions open.
Instructions your experts follow when using this skill.
Use only when the approved role rubric is present. If it is missing, stop and build it first.
The approved role rubric, the resumes — pasted, uploaded, in Drive, or exported from the applicant tracking system (ATS) — and the hiring manager's screen questions if they have any.
Hide names, photos, addresses, graduation dates, and other non-job data when the source lets you. Whether or not it does, never copy them into the record or an EVIDENCE FOUND passage; quote only the job-related text. Never infer age, race, ethnicity, nationality, religion, sex, gender, sexual orientation, disability, health, pregnancy, family status, or any other protected trait.
For each rubric criterion, record:
EVIDENCE FOUND with the resume passage and its location;EVIDENCE MISSING when the document does not state it;CONFIRM IN INTERVIEW when the claim lacks scope, ownership, or result.Do not turn a gap into a negative fact. Do not infer skill from school or employer prestige, a name, dates, location, writing style, or time away from work. Do not compare candidates with each other; compare each record with the same rubric.
An unexplained gap, shrinking scope, a run of very short tenures, or a skill claimed with no artifact behind it is one quoted line under CONFIRM IN INTERVIEW, not a rejection. The named human owner weighs it; the screen never does.
A resume you cannot parse goes on a short "needs a look" list and you move on — never guess its evidence. If many records miss the same must-have, that is a signal the bar or the posting is off: say so as a process-quality note and propose the exact edit, applying it only on the owner's yes.
Return one evidence matrix per candidate, the open verification questions each one raises, and the batch counts (reviewed, evidence-complete, needs interview, needs a look), plus a process-quality note if the rubric yields too many unknowns. Do not rank candidates or recommend advance, reject, hire, or compensation decisions. The named human owner decides and records the reason.
Drafts only. Never reject a candidate, send a decline, or move anyone's stage in the tracker of record without the owner asking for that specific action.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.