Use when a role needs its interview loop planned, the panel needs question banks and anchored scorecards, or tomorrow's interviewers need prep packets.
Instructions your experts follow when using this skill.
A structured kit makes a loop fair and a debrief possible: every candidate for the role meets the same competencies, core questions, and anchored scale. Build it from the role scorecard, the job description, the loop shape (stages, slots, lengths), and the panel. Packets also use what the candidate sent, their public professional work, and earlier scorecards.
Every must-have on the role scorecard gets exactly one owner, so nothing is asked twice or skipped. Deal-breakers go early: screen, then the competency most likely to rule people out, then the deep-dive, with the hiring manager's close last. Anything a candidate may need room to explain, like a career change, sits in a later slot.
Before interview coordination books it, confirm every slot has a competency and the timings fit the day.
Go one competency at a time, four to six questions per slot. Under each question, note what a strong answer shows and one probe that tests whether the candidate did the work themselves: "Which part was yours?", "What number moved?", "What would you change?"
Drop any question that:
Tighten and open up the user's own questions before adding new ones.
Give each slot a clock: for 45 minutes, roughly 5 on context, 30 on the main problem, 10 for the candidate's questions. Warn that the main problem overruns and eats the candidate's time. Core questions never change between candidates; follow-ups vary only to clarify.
Rate each competency 1 to 5: 1 unsatisfactory, 2 below bar, 3 meets bar, 4 above bar, 5 exceptional. Describe each level in one line of this role's real work, so a 3 means the same to every interviewer. Add "not assessed" so nobody guesses at ground they did not cover.
Each rating cites something the candidate said or did. "Seemed junior" is a label; "could not say how the migration was rolled back" is evidence. The card closes with hire or no hire and a one-sentence reason. Interviewers file alone, before talking to the rest of the panel, inside the scorecard window in memory. One scorecard per role. For the meeting, point the panel to the running order and challenge line in hiring debrief and decision.
One page per interview, in slot order. Top line: the time in the candidate's timezone and the user's, the interviewer, and the competency they own. Then:
The evening prep routine runs this pass for tomorrow's loops.
Nothing may touch race, colour, sex, age or graduation year, pregnancy or family plans, health or disability, religion, national origin, marital status, or the language someone speaks at home. Test a language only when the work happens in it. Work authorisation comes up only if their process needs it, as a yes or no. Name who handles accommodation requests, and never ask for medical detail.
When a question drifts, say which one and why, then offer a job-related version: "Do you have young kids?" becomes "The role travels one week a month; does that work for you?"
Kits and packets are drafts. Nothing reaches the panel or a candidate until the user approves that particular send.
The kit (question banks, anchored scorecards, slot timings) in chat and saved to the hiring folder as one file per role; prep packets saved with the date and role in the filename; and one line naming any slot missing an interviewer or a competency.
Nothing from or about the candidate: base the packet on the role scorecard and posting, and flag the summary as thin. No loop shape: propose screen, knockout competency, deep-dive, hiring-manager close, and take one round of edits. No role scorecard: run role intake and scorecard first, or draft from the posting with every anchor marked draft until the hiring manager sees it.
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.