Social Share Generator
Implement or audit on-page social share buttons and share intents so readers can spread articles and product pages without wiring ad-hoc links.
Overview
Social Share Generator is an agent skill most often used in Build (also Launch) that guides adding and optimizing social share buttons and share intent URLs for the current page.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill social-share-generatorWhat is this skill?
- Covers share-current-page buttons (X, LinkedIn, Facebook, WhatsApp)—not footer profile follow links
- Recommends fewer, better-placed buttons over scattered icon farms on article pages
- Ties share UX to open-graph and twitter-cards for correct link previews
- Includes native share and Web Share API patterns where supported
- Version 1.0.1 metadata in skill bundle
Adoption & trust: 747 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your blog or marketing site has missing, cluttered, or wrong share controls, so readers cannot reliably spread your URL with a correct preview.
Who is it for?
Content sites, indie SaaS marketing pages, and ecommerce editorial templates where on-page sharing is still a primary amplification lever.
Skip if: Brand-only social profile links, enterprise social listening suites, or teams that rely exclusively on in-app share with no web article surface.
When should I use this skill?
User wants share buttons, social share, share to X or LinkedIn, share icons, share widget, native share, Web Share API, or share intent URLs.
What do I get? / Deliverables
You get actionable placement and implementation guidance for share buttons and intents, with clear handoff to open-graph and twitter-cards for preview metadata.
- Share button placement and platform intent URL plan
- Implementation notes for Web Share API where applicable
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is the canonical shelf because the skill guides concrete UI implementation—placement, share URLs, Web Share API—not just launch messaging. Frontend subphase fits share widgets, intent URLs, and article-page UX that lives in the site or app template layer.
Where it fits
Wire X and LinkedIn intent URLs on a new changelog template with minimal icon set.
Audit share controls on launch blog post before Product Hunt or newsletter blast.
Remove excess share icons and reposition after analytics show low click-through on sidebar clutter.
How it compares
Implementation skill for share-this-page buttons—pair with open-graph for previews, not a replacement for full social CRM or ad creative workflows.
Common Questions / FAQ
Who is social-share-generator for?
Solo builders and small teams shipping marketing sites or content products who need correct share buttons and intents without guessing platform URL formats.
When should I use social-share-generator?
Use it in Build while implementing article or product templates; at Launch when auditing share UX before a campaign; and in Grow when optimizing placement after engagement data.
Is social-share-generator safe to install?
It is documentation-style frontend guidance; review the Security Audits panel on this Prism page before installing the marketing-skills bundle in your agent.
Workflow Chain
Then invoke: open graph, twitter cards
SKILL.md
READMESKILL.md - Social Share Generator
# Components: Social Share Buttons Guides implementation of **share buttons** that let users share the current page (article, post, product) to social platforms. Distinct from **social profile links** (footer links to your brand's X, LinkedIn, etc.) — share buttons share *this* content. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Share buttons**: Share current page URL to X, LinkedIn, Facebook, WhatsApp, etc. - **Not** social profile links (e.g. "Follow us on X") — those live in footer/nav ## Why It Matters - Websites with visible social share icons tend to see higher social engagement - Share buttons amplify reach; Open Graph and Twitter Cards control preview — see **open-graph**, **twitter-cards** ## Placement (Article Pages) **Fewer, better-placed buttons outperform scattered placement.** Research: removing 80% of buttons and repositioning the remaining 20% at high-emotion moments can **3× conversion** on share actions. | Placement | Best For | Notes | |-----------|----------|-------| | **After first paragraph** | Most articles | Catches speed-readers; visible early | | **Sticky sidebar** | Long-form (desktop) | Always visible; consider hiding on mobile | | **Below title / hero** | Short posts | High visibility | | **End of article** | All | Natural completion point; pair with CTA | | **Mid-article** (after key insight) | Long content | Place at friction points (after surprising stat, before CTA) | **Avoid**: Dozens of icons; every platform when audience uses 2–3. Choose 3–5 platforms that match your audience (e.g. B2B: X, LinkedIn; B2C: X, Facebook, WhatsApp). ## Share URLs (Intent Links) Use platform share/intent URLs so users share with one click: | Platform | Share URL pattern | |----------|-------------------| | **X (Twitter)** | `https://twitter.com/intent/tweet?url={url}&text={text}` | | **LinkedIn** | `https://www.linkedin.com/sharing/share-offsite/?url={url}` | | **Facebook** | `https://www.facebook.com/sharer/sharer.php?u={url}` | | **WhatsApp** | `https://wa.me/?text={url}%20{text}` | | **Telegram** | `https://t.me/share/url?url={url}&text={text}` | Encode `url` and `text` with `encodeURIComponent()`. Use page title or a short pre-written message for `text` — **platform-specific prompts with pre-written messages perform ~4× better than generic icons**. ## Platform Brand Guidelines (Icons) Use official brand assets. Minimum sizes and color rules: | Platform | Min size | Colors | Notes | |----------|----------|--------|-------| | **Facebook** | 16px | Blue #1877F2 or monochrome | No rotation, animation without permission | | **X (Twitter)** | 32px | Black or white only | Use current X logo, not deprecated bird | | **LinkedIn** | 21px height | Blue #0A66C2 or monochrome | Use "in" bug for icons | | **Instagram** | 29×29px | Black, white, or official gradient | Glyph for social icons | Source icons from official brand resource centers. Outdated or non-compliant icons reduce perceived shareability. ## Design & Technical | Item | Guideline | |------|-----------| | **Format** | SVG preferred (scalable, small); PNG/WebP with fallback | | **Performance** | Lightweight; avoid heavy share plugins that slow LCP | | **Accessibility** | `aria-label="Share on X"`; keyboard accessible | | **Mobile** | Touch targets ≥44×44px; consider native share API (`navigator.share`) on mobile |