About make-product-viral
A marketing skill for teams improving product pages and other product surfaces to increase clarity, trust, recall, and shareability. It provides an audit workflow covering the promise, product proof, calls to action, pricing trust, and social previews.
Key features
- 01Checks whether the first viewport explains product and outcome
- 02Moves product demos or proof earlier
- 03Reduces mixed messages and clarifies the main action
- 04Reviews trust signals, pricing, and paywall fit
- 05Checks social previews and the final impression
Use cases
- 01Audit a product landing or pricing page
- 02Improve a launch page, free tool, or app-store surface
- 03Review share previews and conversion paths before launch
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ lvtd-llc/ skills --skill make-product-viralAfter installing, type/make-product-viralin Claude Code to confirm it loaded.
Bundled filesreferences/source-and-caveats.mdworkflows/audit-product-surface.md
Details
From the project READMEMake Product Viral
Use this skill to improve a product surface so people can understand it quickly, trust it before paying, remember it after leaving, and share it without needing to decode the whole page first.
Attribution
This skill is inspired by Marc Lou's "32 Principles of a Viral Product" post on X: https://x.com/marclou/status/2065385672991752210
Use the source as a set of strong defaults from startup building experience, not
as universal rules. See references/source-and-caveats.md for attribution,
ethical guardrails, and adaptation notes.
Core Lens
A viral product is not just a product with social sharing. It has a simple promise, visible product proof, low cognitive load, a clear buying path, and a memorable reason to talk about it.
Optimize in this order:
- Can people understand it in seconds?
- Can they see or try the product before reading a long explanation?
- Is the desired outcome concrete, emotional, and memorable?
- Is there one obvious next action?
- Is trust visible before the user is asked to pay?
- Is the page easy to share, including its final impression and social preview?
Resource Routing
Load only the files needed for the task:
| Need | Read |
|---|---|
| Full audit sequence for a product, landing page, pricing page, launch page, free tool, app-store surface, or OG image | workflows/audit-product-surface.md |
| Attribution, caveats, and ethical guardrails | references/source-and-caveats.md |
Fast Workflow
- Write the product in one clear sentence before making lower-level changes.
- Check whether the first viewport can sell alone: what it is, who it is for, the result, why to believe it, and what happens on click.
- Move visible product proof before long explanatory copy.
- Remove mixed-message sections so each screen or section carries one idea.
- Make the primary CTA specific to the next action.
- Check trust, pricing clarity, and paywall fit before recommending launch traffic.
- Review the social preview and final impression as shareable artifacts.
Output Format
When using this skill, respond with:
- Viral diagnosis: the main reason this is or is not likely to spread.
- Highest-leverage fixes: 3 to 7 changes, ordered by impact.
- Hero rewrite: headline, subhead, CTA, and proof or demo suggestion.
- Shareability pass: OG image, footer or final impression, and one-line description.
- Pricing or paywall note: only if relevant.
- Validation plan: what to check before launch.
Keep recommendations concrete. Prefer replacement copy, section order, product proof, pricing structure, and specific UI/content changes over abstract advice.