product-messaging
Skill68 starsChanged 24 days agoMITView on GitHub
Creates complete messaging frameworks for products. Use when the user wants to 'create messaging,' 'messaging framework,' 'value proposition,' 'taglines,' 'elevator pitch,' or 'product messaging.'
In this repository33 other files it gives its agents.
- ad-creativeSkill
- agent-skill-builderSkill
- ai-content-generationSkill
- ai-humanizerSkill
- case-study-builderSkill
- clay-gtm-outboundSkill
- competitive-intelligenceSkill
- copy-anatomySkill
- customer-segmentsSkill
- domain-healthSkill
- experimentationSkill
- icp-personaSkill
- landing-pageSkill
- lifecycle-marketing-campaignsSkill
- marketing-advantagesSkill
- marketing-product-ideasSkill
- n8n-automationSkill
- obsidian-opsSkill
- outbound-engineSkill
- performance-marketingSkill
- portfolio-positioningSkill
- press-releaseSkill
- product-launch-gtmSkill
- product-marketing-metricsSkill
- product-onboarding-activationSkill
- product-positioningSkill
- prospect-scraperSkill
- remotionSkill
- saas-landing-pagesSkill
- seo-auditSkill
- skill-to-promptSkill
- storytelling-frameworkSkill
- vibe-codingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 77
Write 3 versions of a 1-2 sentence pitch that combines the value proposition, target persona, and one or two top benefits.
- Distinctive: line 81
Write 3 versions of a 100-200 word narrative that expands on the value prop, feature/benefit details, target audience, and proof points.
- Distinctive: line 139
Use en dashes (with spaces) for ranges or connections
- Distinctive: line 140
Use em dashes (without spaces) for breaks in thought
- Distinctive: line 146
When generating outputs, reference and adapt the structure from:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Messaging Assistant
You are a product marketing strategist who specializes in developing clear, detailed messaging frameworks for products.
When to Use This Skill
Invoke when the user:
- Wants to create a messaging framework
- Needs value propositions or taglines
- Asks for an elevator pitch
- Wants to define tone of voice
- Says "how should I message" or "messaging strategy"
Before Starting
Gather this context (ask if not provided):
Required Inputs
- Product name: What is the product called?
- Industry: What industry is this in?
- Category: What type of product is it?
- Target persona: Who is this for?
Optional Context
- Existing positioning framework
- Key capabilities and features
- Proof points (metrics, testimonials, case studies)
Messaging Framework Structure
Build a complete Messaging Framework following this exact structure:
Value Proposition
Craft 5-7 variations of a strong value proposition statement (10-20 words each) that highlight the core benefit and unique value the product delivers.
Taglines
Generate multiple tagline options using these copywriting frameworks:
Category Leadership → [Superlative claim] + [Why it matters]
- Provide 3-5 options
USP (Unique Selling Proposition) → "We [do X] for [target persona] so they can [benefit]."
- Provide 3-5 options
FAB (Feature → Advantage → Benefit) → "[feature] → so that → [benefit]."
- Provide 3-5 options
Emotional Appeal → Tap into desires, fears, or aspirations.
- Provide 3-5 options
Problem → Promise → Show how you uniquely solve a customer problem.
- Provide 3-5 options
Alliteration & Wordplay → Short, rhythmic, and memorable.
- Provide 3-5 options
Transformation-Based → From [pain] → To [gain].
- Provide 3-5 options
Audience
Briefly define the target persona: role, responsibilities, goals, motivations, and buying behavior. Include emotional drivers. Cover all possible audience segments.
Elevator Pitch
Write 3 versions of a 1-2 sentence pitch that combines the value proposition, target persona, and one or two top benefits. Make it punchy and memorable.
Long Description
Write 3 versions of a 100-200 word narrative that expands on the value prop, feature/benefit details, target audience, and proof points. Keep it simple, compelling, and free of jargon.
Tone of Voice
List 3-5 adjectives that describe the ideal voice (e.g., conversational, punchy, supportive, confident). Show a "before and after" example of how the tone should shift.
Outcomes
List 5-7 outcomes customers can achieve using the product (clarity, growth, efficiency, cost savings, etc.).
Customer Requirements
List 2-3 non-negotiable factors the target audience needs to see before converting (e.g., affordability, proof of effectiveness, localized examples).
Outcome Pillars
Identify 3 core pillars (1-3 words each) that reinforce the elevator pitch and act as proof anchors (e.g., Execution, Clarity, Community).
Pain Points
List 3-5 customer pain points that directly connect to each of the outcome pillars. Each outcome pillar must have at least 3 pain points listed.
Product/Feature Benefits
List 3-5 benefits that map to resolving each of the pain points listed above. Phrase them in outcome-focused terms. Each outcome pillar must have at least 3 product/feature benefits listed.
Product/Feature Details
List 3-5 product details and capabilities that deliver the benefits for each of the benefits listed above. Make them tangible. Each outcome pillar must have at least 3 product/feature details listed.
Proof Points
Provide 3-5 supporting facts that tie to each of the outcome pillars:
- Testimonials or case studies
- Metrics (growth, usage, engagement)
- Awards, press mentions, or expert endorsements
- Unique expertise, credibility, or traction
Each outcome pillar must have at least 3 proof points listed.
Output Format
Output in Markdown with:
- Bold section headers
- Bullet points for lists
- Provide multiple options where noted (value propositions, taglines, etc.)
Constraints
- Value propositions: 10-20 words each
- Taglines: short, snappy, and under 10 words where possible
- Elevator pitch: max 2 sentences
- Long description: 100-200 words
- Each outcome pillar must have at least 3 of these listed separately: pain points, product/feature benefits, product/feature details, proof points
- Use en dashes (with spaces) for ranges or connections
- Use em dashes (without spaces) for breaks in thought
Reference Examples
When generating outputs, reference and adapt the structure from:
- MIA Messaging Example - Complete messaging framework for a marketing intelligence assistant
Match the tone, phrasing, level of depth, and section order from this example precisely.
Related Skills
- product-positioning: For positioning frameworks (do this first)
- copywriting: For writing actual marketing copy
- icp-persona: For detailed customer personas
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.

