thatrebeccarae/claude-marketing / skills/social-preview
social-preview
VerifiedGenerate Open Graph social preview images (1280x640) for GitHub repositories. Creates branded OG images that display when repos are shared on Twitter, LinkedIn, and Slack. Supports custom templates, dark/light themes, and automated generation.
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 3.6 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 7.8 KB |
| SKILL.md | skill md | 8.2 KB |
EXAMPLES.md
View on GitHub---
name: social-preview
description: "Usage examples for the social-preview skill."
---
# Social Preview -- Examples
## Example 1: Dark-Theme Social Preview for a CLI Tool
**User:**
```
/social-preview generate ~/projects/my-agent
```
**What happens:**
1. Skill scans the repo: name is `my-agent`, description is "Autonomous AI agent framework", primary language is TypeScript, logo found at `branding/logo.png`.
2. Asks user for template preference. User picks **dark** (default).
3. Generates `social-preview.html`:
```html
<body>
<div class="accent-bar"></div>
<div class="project-name">my-agent</div>
<div class="tagline">Autonomous AI agent framework</div>
<div class="language-badge">TypeScript</div>
<div class="attribution">github.com/your-username</div>
</body>
```
4. Guides user to render via Puppeteer:
```bash
cd ~/projects/my-agent
node -e "const p=require('puppeteer');(async()=>{const b=await p.launch({headless:true});const pg=await b.newPage();await pg.setViewport({width:1280,height:640,deviceScaleFactor:2});await pg.goto('file://$(pwd)/social-preview.html',{waitUntil:'networkidle0'});await pg.screenshot({path:'social-preview.png',clip:{x:0,y:0,width:1280,height:640}});await b.close();})()"
```
5. Instructs user to upload via GitHub Settings > General > Social Preview.
6. Provides Twitter Card Validator URL to verify.
---
## Example 2: Branded Social Preview Matching Project Colors
**User:**
```
/social-preview generate ~/projects/my-tracker
```
**What happens:**
1. Skill scans the repo: name is `my-tracker`, description is "Time tracking with presence", primary language is TypeScript. Detects Tailwind config with custom dark palette (`#08080d` background).
2. Asks user for template. User says: "Use the project's dark palette -- #08080d background, zinc text."
3. Skill modifies the dark template to use the project's brand colors:
```css
body {
background: #08080d;
color: #e4e4e7; /* zinc-200 */
}
.tagline {
color: #a1a1aa; /* zinc-400 */
}
.accent-bar {
background: linear-gradient(90deg, #a78bfa, #818cf8); /* project accent */
}
```
4. Generates HTML, renders to PNG, guides upload.
**Key takeaway:** When a project has established brand colors, adapt the template rather than using defaults. The social preview should feel like it belongs to the project.
---
## Example 3: Audit -- Missing Social Preview
**User:**
```
/social-preview audit ~/projects/my-dashboard
```
**Output:**
```
=== Social Preview Audit: my-dashboard ===
Custom preview set: NO (using auto-generated)
Description: "AI-powered agent orchestration dashboard"
Homepage URL: not set
Recommendations:
- No custom social preview is set. The auto-generated preview shows the
default GitHub template (repo name + avatar). This is a missed opportunity
for any link shared on Twitter, LinkedIn, or Slack.
- Description is present and good length (42 chars). It will display well
as the tagline in a generated preview.
- Consider setting a homepage URL for additional context in OG metadata.
Run /social-preview generate to create one.
```
**User follows up:**
```
/social-preview generate
```
Skill picks up the same repo context, generates a dark-theme preview using the existing description, renders, and walks through the upload flow.
---
## Quick Reference: Common Workflows
| Scenario | Command |
|----------|---------|
| New repo, needs a preview | `/social-preview generate [path]` |
| Check if preview exists | `/social-preview audit [path]` |
| Rebrand -- new colors | `/social-preview generate [path]` (specify brand colors when asked) |
| Major release refresh | `/social-preview generate [path]` (update tagline to mention version) |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |