Your product already has a moment people would share. It's just hidden.
Find the one screen a customer would screenshot and send to a friend, then clear the gates, crops and generic previews that keep it from spreading. Free Claude skill.
Where it came from: A team of agents went through five of my products looking for the moment someone would screenshot and send to a friend.
Ask an owner what makes customers talk about them and you'll usually hear about a feature. Ask what a customer would actually screenshot and text to a friend, and the answer is almost always something smaller and more personal: a result with their own name on it, their own words turned into something useful, a number about their business they didn't know.
We ran this exercise across the products Soxoa operates. Every one of them already had that moment in shipped code. And every one got in its own way in the same few ways.
Read the full article on soxoa.com
/plugin marketplace add johnarndt/soxoa-claude-plugins /plugin install soxoa-ops@soxoa-pluginsDownload screenshot-moment.zipView on GitHub
View SKILL.md
--- name: screenshot-moment description: "Use when a user wants to find the one moment in their product or service that a customer would screenshot and share, and make it easier to share. Triggers include 'what's our wow moment', 'find the holy-shit moment', 'why doesn't anyone share this', 'make this more shareable', 'what would someone post about us', or 'improve our link previews'. Walks the real flow, names the moment that already exists, lists what gets in its way (gates, cropping, missing share, generic previews), and ranks fixes by leverage." --- # Screenshot moment Most products already contain one moment a customer would show to someone else. It is usually buried: behind a form, below the fold, cropped away from the brand, or gone after payment. This skill finds that moment and clears the path to it. It does not invent a new one. ## Inputs - The product or service to review, with access to the flow (a public URL, a staging account, or the code). - Who the customer is and where they would share: a group chat, Slack, LinkedIn, a family text. The destination changes what the moment should look like. ## Workflow 1. **Walk the flow** as a new customer, from first visit to first result. Note every screen where something specific to *them* appears: their name, their data, their words, a result about their business. 2. **Name the moment.** Pick the single screen where the reaction would be "look at this." Describe it in one sentence the way the customer would say it to a friend. It must be real and computed honestly; never propose staging a fake result. 3. **Have a challenger argue.** A second pass (a separate agent or a deliberate rethink) tries to pick a different moment or a different share destination. Keep whichever argument is stronger and note the disagreement. 4. **List what gets in its way**, checking each: - **Gate:** is the moment behind an email form, a card, an allowlist or a hidden toggle? - **Crop:** if someone screenshots just the interesting part, does the brand or URL survive? - **Share:** is there a share button, a copy-link, a download, or a native share sheet? - **Preview:** what does the link preview (title, image, description) show when the link is pasted into a phone chat? A generic card loses the moment. - **Proof:** does the image explain itself? If a result could look hand-made, it should say how it was produced. - **Persistence:** is the moment still there after payment or on a second visit? 5. **Propose fixes** and rank by leverage: people who reach the moment × how much the fix helps ÷ effort. Each fix names the screen or file and what changes. 6. **Deliver** one page per product: the moment, the challenger's view, the blockers, the ranked fixes. Build only what the owner picks. ## Rules - Real data only. Never add fake counts, fake friends' activity or staged results to make something more shareable. - Respect privacy. A shareable card must never expose another customer's data, and the person sharing must see exactly what will be shared. - Mark anything you inferred from code or screenshots rather than saw running as unverified.