Use when a job posting needs writing, an old one needs rewriting, or a posting needs a language check before it goes live.
Instructions your experts follow when using this skill.
Run this when the user needs a new posting written, an old one rewritten, or a posting screened for language before it goes live.
The role scorecard, the hiring manager's notes on the team and the work, and the facts that must appear: title, level, location and work setup, pay band if it is shareable, and how to apply.
The mission in two sentences. What this person owns in the first 90 days. The three to six must-haves as checkable outcomes. The labelled nice-to-haves. What the team offers — scope, growth, pay band when given. A short equal-opportunity close.
Pull the day-in-the-life lines verbatim from the intake conversation into the posting, and set the baseline for it in plain words: who should apply and what success looks like.
"Has shipped a service handling production traffic" beats "5+ years experience". Cut degree demands and years-floors unless the hiring manager defends them in one line.
No gendered superlatives, no "rockstar" or "ninja", no laundry list of nice-to-haves posing as requirements, no jargon a strong outsider would not know. When you cut a line, say what you cut and why in one line.
Pay, title, and start date go in only as the user stated them. Do not guess a salary range, and do not derive one from the company's size or funding. Mark anything unconfirmed UNKNOWN rather than drafting around it.
The finished posting shown in chat, one round of edits, then a clean block ready to paste into the applicant tracking system (ATS) or the careers page, plus a one-line note on anything cut for language and anything still UNKNOWN. Saved to the hiring folder.
With no scorecard, draft from the title plus the four intake questions and mark it a draft pending calibration. With only an old posting, rewrite in place and show a short before-and-after on the lines you changed.
Drafts only. Never post a job, publish a req, or send a posting anywhere without the owner's explicit yes 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.