- Home
- Skills
- Marketing & SEO
- Product Marketing Context
More screenshots
Works with the AI Agents you already use
Product Marketing Context
Build one living brief — who buys, why it hurts, why you win, how you speak, what you're aiming at — so every campaign, launch, and page starts from the same ground instead of repeat questions.
$5
Product Marketing Context
Example session with this skill installed
We sell a scheduling tool for dog groomers. Our site says "salon software for pet professionals," our ads say "booking app," and my partner describes it as "a front desk in your pocket." Build us the brief — at least the skeleton with our gaps marked honestly.
- Read your context and instructions
- Compiled the product marketing context
Route decision: the product is live with paying customers and artifacts exist, so draft-from-repo, corrected against the team's three descriptions. The three taglines are the first finding — they name three different products (back-office software, a booking widget, a receptionist replacement). The brief forces one answer.
Who buys (drafted, 2/2): solo groomers and 2–4 chair salons; the owner is the buyer, the bather is the daily user whose complaints carry veto weight. Jobs hired for: stop phone-tag bookings, stop no-shows, fill Tuesday gaps.
What hurts (1/2, gap marked): sharpest frustration in the owner's words from a support thread — "I spend my lunch break returning booking calls." Cost attached: roughly an hour a day. [NEEDS: no-show rate — the partner quotes 15%, the booking data has never been pulled.]
Why we win (2/2): alternatives are paper diaries (no reminders), generic salon software (built for human hair, pricing and intake forms mismatch), and doing nothing. Top objection — "my clients just text me" — answered honestly: texting works until two clients text at once mid-groom; the tool's edge is the reminder sequence, not the calendar. Anti-persona: mobile groomers working from vans — no fixed front desk, different workflow, named as not-a-fit.
How we speak (1/2): keep "front desk in your pocket" — it is the partner's phrase but customers repeat it back in reviews, so it wins the tagline fight on evidence. Retire "pet professionals" (owners say "groomers"). [NEEDS: one writing sample the team agrees sounds right.]
What we're aiming at (1/2): one action — start a trial from the pricing page. [NEEDS: current trial and conversion numbers.]
Score: 7/10 with no zeros — not shippable yet. The three NEEDS markers are the agenda for one 30-minute sitting, after which this brief, not three taglines, is what every ad and page gets written from.
Connects securely to your tools. The creator never sees your data.
About this skill
Every marketing task asks the same five questions: who is this for, what hurts them, why pick us, what do we sound like, what are we aiming at. Without a brief, each task re-asks them — and gets slightly different answers, which is how positioning drifts until nobody describes the product the same way twice. This skill answers once, in a document that lives with the project and is revised as you learn.
The method is five conversations, worked one at a time and confirmed as you go: Who (buyers, roles, the jobs they hire the product for), Hurts (the sharpest frustration, in the customer's words, with its cost attached), Wins (alternatives and their shortfalls, the top three objections with honest answers, and the anti-persona — who should never buy), Speaks (verbatim customer phrases, words to use and never use, voice, glossary), and Aims (the goal, the one conversion action, the numbers you already know).
You can draft from the repo — README, landing page, pricing page, existing copy — and correct the draft, or interview from scratch using the built-in question bank. A decision point tells you which route fits. A completeness rubric scores each conversation 0–2 (ship at 8+/10, no zeros), three read-back tests check the draft the way strangers, sales reps, and copywriters will use it, and gaps are marked [NEEDS: ...] rather than invented.
Maintenance is part of the skill: versioning rules, an update decision table separating real changes from typo fixes, trigger-based revisits instead of calendar reviews, and a change log that makes positioning drift visible. The worked fragment shows a fictional property-management tool's brief scored section by section.
- The brief is only as true as its inputs — the rubric and NEEDS markers expose gaps, but closing them takes a real conversation, not a better prompt.
- Draft-from-repo inherits whatever drift already lives in your artifacts; the read-back tests catch much of it, but a founder review pass is still required.
- It deliberately will not invent proof: metrics, quotes, and customer names enter the brief only when you supply them.
- One brief per product — teams with a suite will maintain several, which is the point, but it is several documents to keep alive.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
No special permissions declared or detected