Build a job-related hiring rubric with observable anchors before any candidate is screened or interviewed.
Instructions your experts follow when using this skill.
Build the rubric before reading a resume. It tests evidence for the role; it does not describe an ideal person.
Derive four to seven criteria from the approved role outcomes. For each, write:
A one means the evidence method was completed and found no qualifying evidence. A two means partial or indirect evidence. A three means clear evidence at the required scope. A four means clear evidence at greater scope with a stated result. When the source or method is unavailable, or the criterion was not yet tested, mark it "not assessed", not one or zero. A resume that simply omits a criterion is "not assessed" until the interview or work sample tests it.
Do not score protected traits or proxies. Do not score polish, likability, shared interests, school prestige, employer prestige, career gaps, names, addresses, photos, accents, or "culture fit". A communication criterion must name the work product and the level the role needs.
Return the rubric table, weight or equal-weight choice, evidence rules, disallowed signals, and owner approval line. The rubric supports a human decision; it never produces an automatic advance or rejection.
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.