social-share-generator
When the user wants to add, optimize, or audit social share buttons (share article to X, LinkedIn, Facebook, etc.). Also use when the user mentions "share buttons," "social share," "share to X," "share to LinkedIn," "social sharing," "share icons," "share widget," "native share," "Web Share API," or "share intent URLs." For link previews, use open-graph.
What this skill does
# 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 |
## Native Share API (Mobile)
On supported browsers, `navigator.share` lets users share via system dialog (includes more apps). Fallback to intent links when unsupported:
```javascript
if (navigator.share) {
navigator.share({ title, url, text }).catch(() => {});
} else {
window.open(shareUrl, '_blank', 'noopener');
}
```
## Output Format
- **Placement** recommendation for page type
- **Platforms** to include (3–5)
- **Share URL** examples with placeholders
- **Icon** guidelines (size, source)
- **Accessibility** checklist
## Related Skills
- **article-page-generator**: Share buttons on article pages; placement after intro, end of article
- **blog-page-generator**: Share buttons on blog index and post cards
- **open-graph**: OG tags control share preview (og:image, og:title, etc.) — required for share buttons to show rich cards on Facebook, LinkedIn
- **twitter-cards**: Twitter Cards control X preview — required for share buttons to show rich cards when shared to X
- **footer-generator**: Footer has social *profile* links (Follow us); this skill is for *share* buttons (share this page)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.