product-marketing-personas
Skill1 starsChanged 4 days agoMITView on GitHub
Draft or critique product-marketing copy by selecting a buyer-centered reasoning persona: growth guide, infrastructure strategist, or working operator. Use for landing pages, launches, migrations, enterprise pages, pricing, product pages, industry pages, and customer stories; do not use to imitate a named company or reproduce recognisable brand language.
In this repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-componentsSkill
- apple-hig-foundationsSkill
- apple-hig-getting-startedSkill
- apple-hig-inputsSkill
- apple-hig-patternsSkill
- apple-hig-technologiesSkill
- apple-sheetsSkill
- batch-commitSkill
- fluid-interface-designSkill
- git-change-controlSkill
- improve-animationsSkill
- marketing-art-directionSkill
- marketing-product-mediaSkill
- marketing-reference-forensicsSkill
- marketing-visual-qaSkill
- message-delivery-integritySkill
- production-verificationSkill
- security-auditSkill
- systems-builder-writingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read references/personas.md after choosing.
- Distinctive: line 20
Write only from supplied or verified facts.
- Distinctive: line 26
Use contrast only to sharpen a verified truth.
- Distinctive: line 27
Ask a question only when a missing fact would materially change the proposition.
- Distinctive: line 28
Keep rationale separate from customer-facing copy unless the user asks for it.
- Distinctive: line 32
Prefer to know the page role, buyer, maturity, daily job or business model, product behavior, credible evidence, primary objection, buying …
- Distinctive: line 36
Follow the requested format.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Marketing Personas
Choose the persona that best matches the buyer's decision, then build an original argument from verified product facts. A persona is a reasoning model, not a costume or phrase bank.
Choose the persona
- Growth guide — for self-serve products, new businesses, launches, migration, expansion, and audiences that need momentum and a credible next step.
- Infrastructure strategist — for technical platforms, enterprise systems, complex integrations, and buyers who need mechanism, proof, reliability, and adoption reassurance.
- Working operator — for products embedded in daily work, including payments, hardware, scheduling, retail, services, and operational software where workflow and cost clarity matter.
Read references/personas.md after choosing. If the request is page-specific, also read references/page-modes.md. Use one dominant persona. A secondary persona may influence a section when the buying situation genuinely changes, but do not blend all three into a generic voice.
Working rules
- Write only from supplied or verified facts. Never invent metrics, customer names, prices, availability, regulatory claims, specifications, competitive comparisons, or results.
- Establish one dominant commercial argument before polishing sentences.
- Move from outcome to mechanism to proof to the appropriate next action. Do not substitute feature volume for an argument.
- Match technical density and reassurance to the buyer. Preserve implementation, migration, procurement, reliability, and support detail when those concerns affect the decision.
- Translate capabilities into observable product behavior or a concrete moment in the customer's work.
- Match the call to action to the buying motion: self-serve setup, purchase, migration help, consultation, or sales conversation.
- Use contrast only to sharpen a verified truth. Do not manufacture an enemy, false urgency, or a superiority claim.
- Ask a question only when a missing fact would materially change the proposition. Otherwise state the assumption briefly and continue.
- Keep rationale separate from customer-facing copy unless the user asks for it.
Useful inputs
Prefer to know the page role, buyer, maturity, daily job or business model, product behavior, credible evidence, primary objection, buying motion, locale, and intended conversion action.
Deliverable
Follow the requested format. When none is specified, provide:
- the selected persona and why it fits, in one sentence;
- a concise page or message map;
- ready-to-use copy;
- a short list of missing proof or facts that would materially strengthen it.
For research, comparison, or persona refinement, read references/calibration.md. Do not browse merely to decorate ordinary drafting with external references.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

