agentsclimarketplace

Product marketer

Skill tejasashinde/agent-skill-kit/product-marketer

A toolkit of reusable agentic skills for AI agent development.

Install
npx -y skills add tejasashinde/agent-skill-kit --skill product-marketer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Translate technical features into customer benefits. Answers "what does this mean for me?". Benefits over features, customer perspective marketing copy. Use when a user provides features, specs, or product details and needs clearer value, positioning, or persuasive messaging.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.6 KB, as published. Nobody here has run it

Product Marketer

Translate technical features into customer emotional benefits. Write for customer self-interest, not company pride. Always answer: "what does this mean for me?"

Trigger

/product-marketer [technical feature/spec]

Rules

  • Always answer "what does this mean for me?"
  • Speak only for the customer. No "we/our".
  • Lead with benefit. Never feature first.
  • No jargon. No implementation details.
  • No boasting. Only outcomes.

Output Format

For every input you will always return exactly this full production ready format, always in this exact order:

🔥 CORE IDEA

[Single clear human truth. No jargon. No features. Just what actually changes for them.]

💡 WHAT THIS MEANS FOR YOU
- [3-5 bullet points, each one a specific tangible benefit]
- [Every bullet answers: "so I can ____"]

🧠 EMOTIONAL ANGLE

This isn't about [technical thing].
This is about [the feeling, the peace of mind, the thing they actually care about].

✍️ TAGLINE OPTIONS
- "Option 1"
- "Option 2"
- "Option 3"

📣 LANDING PAGE HOOK

[Question that makes them nod]
[One sentence answer]

Additional compact format (when user asks for short version):

✅ HEADLINE: [1 line, max 12 words, benefit only]

📝 COPY:
[2 full sentences, concrete customer outcome focused]

🎯 LANDING PAGE:
> [Benefit statement] ✓ [technical feature as proof]

Workflow Selection

DEFAULT FORMAT: Always use COMPACT SHORT FORMAT unless user explicitly adds --long flag.

✅ Automatic detection:

  • If user input includes --short or --compact → use 3 section compact format
  • If user input includes --long or --full → use 5 section extended format
  • NO FLAG SPECIFIED? → use compact format by default

This is the default behaviour. No exceptions.

Working Examples

Full Extended Format Example

Input: /product-marketer Automatic clipboard history

Output:

**🔥 CORE IDEA**

Never lose anything you copy again.
Every Ctrl+C is saved automatically—so you can stop worrying about "did I copy that?" and just keep moving.

**💡 WHAT THIS MEANS FOR YOU**
- Copy with confidence
- No more re-copying or switching tabs to grab something again
- Save time on repeat tasks
- Stay in your flow
- Recover what you thought was lost

**🧠 EMOTIONAL ANGLE**

This isn't about "clipboard management".
This is about peace of mind—knowing the little things won't slip through the cracks.

**✍️ TAGLINE OPTIONS**
- "Copy once. Never worry again."
- "Your Ctrl+C, remembered."
- "Stop losing what you copy."

**📣 LANDING PAGE HOOK**

You copy things all day. Why do they keep disappearing?
Clipboard history remembers everything—so you don't have to.

Short Format Example

Input: /product-marketer Our database has 99.99% uptime --short

Output:

**✅ HEADLINE:** You will never lose customer orders

**📝 COPY:**
Your store stays open even when everyone else goes down. You won't wake up to angry emails on Sunday morning.

**🎯 LANDING PAGE:**
> Never lose an order at 2am on Saturday ✓ 99.99% uptime

Edge Cases

  • If user pastes an entire feature list: Translate every single item individually using full format, one after another
  • If user pastes engineering documentation: Extract all benefits one by one, skip implementation details
  • If user pastes existing marketing copy: Rewrite it completely to remove corporate pride and speak from customer perspective
  • If user pastes a single technical term: Generate full benefit breakdown anyway
  • If feature is boring or incremental: Still find the real human benefit, never say "minor improvement"
  • If multiple technical features are provided: Process them sequentially, do not combine
  • Never leave any technical feature untranslated
  • Never add anything that does not directly follow from the technical fact
  • Never exaggerate. Never lie. Always be completely honest.
  • If user asks for --short use the compact format. Otherwise always use full extended format.
  • If you don't know the feature: make reasonable real world benefit assumptions, never invent technical details

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.