[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77STV3M2B5JJ6JSZP2GF517":3,"skill-same:01M77STV3M2B5JJ6JSZP2GF517":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77STV3M2B5JJ6JSZP2GF517","make-product-viral",null,"Make a product, landing page, pricing page, launch page, free tool, or social preview easier to understand, buy, remember, and share using Marc Lou-inspired viral product patterns.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmake-product-viral\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: make-product-viral\ndescription: Make a product, landing page, pricing page, launch page, free tool, or social preview easier to understand, buy, remember, and share using Marc Lou-inspired viral product patterns.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Make Product Viral\n  category: Marketing\n  tags: marketing,launch,cro,pricing,copywriting,shareability\n---\n\n# Make Product Viral\n\n## Attribution\n\nThis skill is inspired by Marc Lou's \"32 Principles of a Viral Product\" post on X:\nhttps:\u002F\u002Fx.com\u002Fmarclou\u002Fstatus\u002F2065385672991752210\n\nMarc framed the source ideas as patterns from five years of building startups in\npublic, not as universal rules. Keep that spirit: use the principles as strong\ndefaults, then adapt them to the product, audience, price point, and channel.\n\nDo not copy Marc's original post wholesale into outputs. Attribute the framework\nwhen the user asks where the ideas came from or when the output presents this as\na named audit method.\n\n## Core Lens\n\nA viral product is not just a product with social sharing. It has a simple\npromise, visible product proof, low cognitive load, a clear buying path, and a\nmemorable reason to talk about it.\n\nOptimize in this order:\n\n1. Can people understand it in seconds?\n2. Can they see or try the product before reading a long explanation?\n3. Is the desired outcome concrete, emotional, and memorable?\n4. Is there one obvious next action?\n5. Is trust visible before the user is asked to pay?\n6. Is the page easy to share, including its final impression and social preview?\n\n## Fast Audit\n\nUse this sequence when reviewing a product, landing page, launch page, pricing\npage, free tool, app-store surface, or OG\u002Fsocial preview.\n\n### 1. One Thing\n\nThe product should be describable in under 10 words. The page should sell one\nmain outcome, not a bundle of unrelated capabilities.\n\nCheck for:\n\n- A specific audience or use case.\n- One memorable promise.\n- A clear category, alternative, or comparison anchor.\n- No hero copy that tries to serve every possible buyer at once.\n\nIf the page lacks a sharp one-line description, write that before making\nlower-level suggestions.\n\n### 2. Hero That Can Sell Alone\n\nAssume many visitors will not scroll. The first viewport should answer:\n\n- What is this?\n- Who is it for?\n- What result do I get?\n- Why should I believe it?\n- What happens if I click?\n\nPrefer concrete outcomes over adjectives. Replace vague claims like \"faster\" or\n\"better\" with numbers, time saved, money made, risk reduced, or pain removed\nwhen evidence exists. If evidence does not exist, recommend how to gather it.\n\n### 3. Show Product Before Explaining\n\nA demo, interactive example, annotated screenshot, calculator, scanner, or short\nfounder walkthrough usually beats paragraphs of copy.\n\nFor AI and software products, look for a way to let users experience the payoff\non the page before they create an account. If a hard paywall is appropriate,\nstill show enough product proof to create desire and trust.\n\n### 4. One Screen, One Idea\n\nEach major section should communicate one idea:\n\n- problem\n- product proof\n- outcome\n- social proof\n- pricing\n- comparison\n- objections\n- final shareable close\n\nIf a section mixes several arguments, split it or cut it until the scan path is\nobvious.\n\n### 5. CTA Clarity\n\nUse one primary CTA. The CTA should say what happens next, not a generic action.\n\nWeak patterns:\n\n- Get Started\n- Learn More\n- Submit\n\nStronger patterns:\n\n- Analyze My Website\n- Generate My Launch Page\n- See Pricing\n- Buy the Template\n- Run the Audit\n\nOnly include a secondary CTA when it serves the same buying journey, such as\nwatching a demo or viewing pricing.\n\n### 6. Pricing And Paywall\n\nFor simple indie products, default to clear paid validation over free-user\naccumulation unless the business model truly depends on a free tier.\n\nConsider:\n\n- Is pricing visible from navigation or early page flow?\n- Are there three or fewer choices?\n- Is one plan the obvious best fit?\n- Could a one-time payment sell better than a subscription?\n- Does the product need a tight trial with payment required, especially for\n  app-store-style products?\n\nDo not apply this blindly. SaaS with recurring infrastructure, collaboration,\nongoing service delivery, or high expansion value may need subscriptions.\nFreemium can work when free usage is a distribution channel, proof engine, or\nnetwork-effect driver.\n\n### 7. Copy Only This Founder Could Write\n\nGeneric copy is easy to ignore and easy to copy. Look for founder experience,\nspecific customer language, sharp opinions, or proof from real use.\n\nUse customer words when available. If customer research is missing, ask for\nreviews, support tickets, DMs, interviews, beta feedback, or demo-call notes\nbefore inventing proof.\n\n### 8. Trust Before Traffic\n\nDo not send serious launch traffic to a page with no proof.\n\nMinimum proof can include:\n\n- specific beta-user quotes\n- founder demo video\n- named testimonials\n- before-and-after examples\n- public build-in-progress evidence\n- case-study numbers\n- credible comparison against alternatives\n\nIf testimonials do not exist, recommend a beta-feedback sprint before a bigger\nlaunch.\n\n### 9. Social Preview As Thumbnail\n\nTreat the OG image like a YouTube thumbnail: it should earn the click without\nrequiring the full page.\n\nCheck for:\n\n- one clear message\n- strong contrast\n- readable text if text is used\n- recognizable product, result, or emotion\n- no dense screenshot walls\n- no tiny UI text that only makes sense after zooming\n\nMarc clarified in the thread that overly text-heavy thumbnails can fail because\npeople will not stop to decode them. If the OG image has a lot of text, ask:\n\"How would this look with roughly 180 characters or less?\"\n\n### 10. Memorable Final Impression\n\nThe footer or final section should not feel like a dead end. End with something\npeople can remember or share:\n\n- a strong one-line promise\n- a pointed comparison\n- a founder note\n- a compact demo or result\n- a final CTA tied to the product's core action\n\n## Output Format\n\nWhen using this skill, respond with:\n\n1. **Viral diagnosis:** the main reason this is or is not likely to spread.\n2. **Highest-leverage fixes:** 3 to 7 changes, ordered by impact.\n3. **Hero rewrite:** headline, subhead, CTA, and proof or demo suggestion.\n4. **Shareability pass:** OG image, footer or final impression, and one-line\n   description.\n5. **Pricing or paywall note:** only if relevant.\n6. **Validation plan:** what to check before launch.\n\nKeep recommendations concrete. Prefer replacement copy, section order, product\nproof, pricing structure, and specific UI\u002Fcontent changes over abstract advice.\n\n## Caveats\n\n- Attribute the source when presenting the framework: inspired by Marc Lou's\n  viral product principles.\n- Treat the principles as strong defaults, not commandments.\n- Avoid fake testimonials, fake scarcity, manipulative claims, or unsupported\n  numbers.\n- Strong claims need evidence. If evidence is missing, recommend how to gather\n  it.\n- Do not let \"viral\" override usefulness. A product that spreads but disappoints\n  users creates the wrong kind of attention.\n","# Make Product Viral\n\n## Attribution\n\nThis skill is inspired by Marc Lou's \"32 Principles of a Viral Product\" post on X:\nhttps:\u002F\u002Fx.com\u002Fmarclou\u002Fstatus\u002F2065385672991752210\n\nMarc framed the source ideas as patterns from five years of building startups in\npublic, not as universal rules. Keep that spirit: use the principles as strong\ndefaults, then adapt them to the product, audience, price point, and channel.\n\nDo not copy Marc's original post wholesale into outputs. Attribute the framework\nwhen the user asks where the ideas came from or when the output presents this as\na named audit method.\n\n## Core Lens\n\nA viral product is not just a product with social sharing. It has a simple\npromise, visible product proof, low cognitive load, a clear buying path, and a\nmemorable reason to talk about it.\n\nOptimize in this order:\n\n1. Can people understand it in seconds?\n2. Can they see or try the product before reading a long explanation?\n3. Is the desired outcome concrete, emotional, and memorable?\n4. Is there one obvious next action?\n5. Is trust visible before the user is asked to pay?\n6. Is the page easy to share, including its final impression and social preview?\n\n## Fast Audit\n\nUse this sequence when reviewing a product, landing page, launch page, pricing\npage, free tool, app-store surface, or OG\u002Fsocial preview.\n\n### 1. One Thing\n\nThe product should be describable in under 10 words. The page should sell one\nmain outcome, not a bundle of unrelated capabilities.\n\nCheck for:\n\n- A specific audience or use case.\n- One memorable promise.\n- A clear category, alternative, or comparison anchor.\n- No hero copy that tries to serve every possible buyer at once.\n\nIf the page lacks a sharp one-line description, write that before making\nlower-level suggestions.\n\n### 2. Hero That Can Sell Alone\n\nAssume many visitors will not scroll. The first viewport should answer:\n\n- What is this?\n- Who is it for?\n- What result do I get?\n- Why should I believe it?\n- What happens if I click?\n\nPrefer concrete outcomes over adjectives. Replace vague claims like \"faster\" or\n\"better\" with numbers, time saved, money made, risk reduced, or pain removed\nwhen evidence exists. If evidence does not exist, recommend how to gather it.\n\n### 3. Show Product Before Explaining\n\nA demo, interactive example, annotated screenshot, calculator, scanner, or short\nfounder walkthrough usually beats paragraphs of copy.\n\nFor AI and software products, look for a way to let users experience the payoff\non the page before they create an account. If a hard paywall is appropriate,\nstill show enough product proof to create desire and trust.\n\n### 4. One Screen, One Idea\n\nEach major section should communicate one idea:\n\n- problem\n- product proof\n- outcome\n- social proof\n- pricing\n- comparison\n- objections\n- final shareable close\n\nIf a section mixes several arguments, split it or cut it until the scan path is\nobvious.\n\n### 5. CTA Clarity\n\nUse one primary CTA. The CTA should say what happens next, not a generic action.\n\nWeak patterns:\n\n- Get Started\n- Learn More\n- Submit\n\nStronger patterns:\n\n- Analyze My Website\n- Generate My Launch Page\n- See Pricing\n- Buy the Template\n- Run the Audit\n\nOnly include a secondary CTA when it serves the same buying journey, such as\nwatching a demo or viewing pricing.\n\n### 6. Pricing And Paywall\n\nFor simple indie products, default to clear paid validation over free-user\naccumulation unless the business model truly depends on a free tier.\n\nConsider:\n\n- Is pricing visible from navigation or early page flow?\n- Are there three or fewer choices?\n- Is one plan the obvious best fit?\n- Could a one-time payment sell better than a subscription?\n- Does the product need a tight trial with payment required, especially for\n  app-store-style products?\n\nDo not apply this blindly. SaaS with recurring infrastructure, collaboration,\nongoing service delivery, or high expansion value may need subscriptions.\nFreemium can work when free usage is a distribution channel, proof engine, or\nnetwork-effect driver.\n\n### 7. Copy Only This Founder Could Write\n\nGeneric copy is easy to ignore and easy to copy. Look for founder experience,\nspecific customer language, sharp opinions, or proof from real use.\n\nUse customer words when available. If customer research is missing, ask for\nreviews, support tickets, DMs, interviews, beta feedback, or demo-call notes\nbefore inventing proof.\n\n### 8. Trust Before Traffic\n\nDo not send serious launch traffic to a page with no proof.\n\nMinimum proof can include:\n\n- specific beta-user quotes\n- founder demo video\n- named testimonials\n- before-and-after examples\n- public build-in-progress evidence\n- case-study numbers\n- credible comparison against alternatives\n\nIf testimonials do not exist, recommend a beta-feedback sprint before a bigger\nlaunch.\n\n### 9. Social Preview As Thumbnail\n\nTreat the OG image like a YouTube thumbnail: it should earn the click without\nrequiring the full page.\n\nCheck for:\n\n- one clear message\n- strong contrast\n- readable text if text is used\n- recognizable product, result, or emotion\n- no dense screenshot walls\n- no tiny UI text that only makes sense after zooming\n\nMarc clarified in the thread that overly text-heavy thumbnails can fail because\npeople will not stop to decode them. If the OG image has a lot of text, ask:\n\"How would this look with roughly 180 characters or less?\"\n\n### 10. Memorable Final Impression\n\nThe footer or final section should not feel like a dead end. End with something\npeople can remember or share:\n\n- a strong one-line promise\n- a pointed comparison\n- a founder note\n- a compact demo or result\n- a final CTA tied to the product's core action\n\n## Output Format\n\nWhen using this skill, respond with:\n\n1. **Viral diagnosis:** the main reason this is or is not likely to spread.\n2. **Highest-leverage fixes:** 3 to 7 changes, ordered by impact.\n3. **Hero rewrite:** headline, subhead, CTA, and proof or demo suggestion.\n4. **Shareability pass:** OG image, footer or final impression, and one-line\n   description.\n5. **Pricing or paywall note:** only if relevant.\n6. **Validation plan:** what to check before launch.\n\nKeep recommendations concrete. Prefer replacement copy, section order, product\nproof, pricing structure, and specific UI\u002Fcontent changes over abstract advice.\n\n## Caveats\n\n- Attribute the source when presenting the framework: inspired by Marc Lou's\n  viral product principles.\n- Treat the principles as strong defaults, not commandments.\n- Avoid fake testimonials, fake scarcity, manipulative claims, or unsupported\n  numbers.\n- Strong claims need evidence. If evidence is missing, recommend how to gather\n  it.\n- Do not let \"viral\" override usefulness. A product that spreads but disappoints\n  users creates the wrong kind of attention.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"marketing,launch,cro,pricing,copywriting,shareability","0.1.0","Marketing","Make Product Viral","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmake-product-viral","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill make-product-viral",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill make-product-viral",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill make-product-viral","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmake-product-viral\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fapp-icon.png","ASSET","资产文件",325758,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmake-product-viral\u002Fassets\u002Fapp-icon.png",[56,65,72,80,87,94],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]