Agent skill
social-graphic
Create social media graphics and visual assets for any platform. Use when asked to create a social media image, newsletter header, blog feature image, OG image, profile banner, or when the user mentions 'social graphic', 'header image', 'banner', or needs a platform-specific visual asset (not thumbnails — use creator-stack:thumbnail for those).
Install this agent skill to your Project
npx add-skill https://github.com/kenneth-liao/ai-launchpad-marketplace/tree/main/creator-stack/skills/social-graphic
SKILL.md
Social Graphic Skill
Create polished social media graphics and visual assets optimized for specific platforms. This skill handles platform-specific dimensions, safe zones, and design constraints to produce assets that display correctly and perform well across channels.
When to Use
Invoke this skill when the user needs:
- Social media post images -- Twitter/X, LinkedIn, Instagram
- Newsletter headers -- Substack, email campaigns
- Blog feature images -- OG images, hero banners
- Course thumbnails -- Platform-specific cover images
- Profile and cover images -- Headers, banners, profile pictures
For YouTube thumbnails or any thumbnail requiring specialized CTR optimization, use the creator-stack:thumbnail skill instead.
Platform Resolution
Before generating any asset, determine the target platform and format. Platform specs are loaded from references/platform-specs.md.
Resolution order:
- If the calling orchestrator provides platform context (dimensions, format), use it directly
- If the user specifies a platform, load specs from the reference file
- If ambiguous, ask the user which platform and format they need
Always confirm dimensions before generating. Mismatched dimensions cause cropping, letterboxing, or blurry upscaling on the target platform.
Standard Workflow
1. Determine Platform and Format
Identify the target platform and specific format from user request or orchestrator context. Load the matching specs from references/platform-specs.md, including dimensions, aspect ratio, safe zones, and text constraints.
2. Gather Context
Collect the information needed to design the graphic:
- Topic or subject -- What the graphic is about
- Key message -- The primary text or call to action
- Brand elements -- Logo, colors, typography (resolve via brand guidelines)
- Reference images -- Any existing assets, style references, or photos to incorporate
- Tone -- Professional, casual, bold, minimal, etc.
3. Design the Concept
Create a design concept that respects the platform constraints:
- Work within the safe zone (keep text and key elements within 80% of frame)
- Follow text size minimums from platform specs
- Ensure the composition works at the platform's typical display size
- Apply the thumbnail design principles from
creator-stack:thumbnailreferences where applicable (glance test, focal points, contrast)
4. Generate the Image
Use the creator-stack:nanobanana skill to generate the graphic:
- Set the correct aspect ratio matching the platform spec
- Use Pro model for final production assets, Flash for drafts and exploration
- Pass any reference images using absolute paths
- Include brand-specific style direction in the prompt
5. Brand Compliance Check
Invoke creator-stack:brand-guidelines to verify the generated graphic against:
- Brand color palette and typography
- Visual style consistency
- Anti-patterns (things the brand should never do)
- Design system rules for the asset type
For The AI Launchpad assets, this step is mandatory. For other brands, check if a brand guidelines skill exists at ~/.claude/skills/ and apply any relevant constraints.
6. Review and Iterate
Review the generated graphic against the quality checklist below. If it does not pass, edit using creator-stack:nanobanana with the original as a reference image. Limit iteration to two rounds maximum.
7. Present to User
Present the final graphic with:
- The generated image
- Platform and dimensions used
- Any notes on safe zones or cropping behavior
- Suggestions for companion text or alt text
Brand Compliance
When creating visual assets for The AI Launchpad, invoke creator-stack:brand-guidelines to resolve the correct design system and check anti-patterns. This ensures all social graphics are consistent with the established brand identity.
For other brands, check if a brand guidelines skill exists at ~/.claude/skills/ and apply any relevant design constraints. If no brand guidelines exist, follow general best practices for the target platform.
Quality Checklist
Before presenting any graphic to the user, verify:
- Correct dimensions -- Matches the target platform spec exactly
- Safe zone compliance -- Text and key elements within 80% of frame
- Text legibility -- All text readable at the platform's typical display size
- Brand consistency -- Colors, fonts, and style match brand guidelines
- Visual clarity -- Clean composition, clear focal point, no clutter
- Platform constraints -- Respects text overlay limits, file size recommendations
- Contrast and accessibility -- Sufficient contrast for readability across devices
- No cropping issues -- Key elements will not be cut off by platform UI overlays
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
test-skill
Run or generate test suites for any skill. Use when testing a skill before deployment, after making changes, before/after plugin upgrades, when validating skill behavior, or when the user says "test skill", "run skill tests", "generate tests for skill", or "check for regressions".
upgrade-plugin
Upgrade a plugin's skills, hooks, and patterns to align with latest Claude Code capabilities and best practices. Use when a plugin needs modernization, after Claude Code updates, or when the user says "upgrade plugin", "modernize plugin", or "update plugin to latest patterns".
skill-retro
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
view-team-session
Generate a self-contained HTML viewer for any Claude Code session, including agent team sessions with full inter-agent DM timelines. Use whenever the user asks to "view a session", "visualize a conversation", "show me what happened in session X", "generate a session viewer", "replay a session", "show me what my agents did", "session replay", "team timeline", or references viewing/inspecting Claude Code JSONL logs. Also use when the user provides a session ID and wants to see the conversation.
analyze-team-session
Use when reviewing an agent team session export for quality, when asked to "analyze this team session", "review my agent team run", "what went wrong with this session", "how can I improve my agent team usage", or when provided a markdown team session transcript and asked for feedback on agent teams effectiveness.
youtube-data
Retrieve YouTube data using the YouTube Data API. Use when you need to search videos, get video or channel details, fetch transcripts, read comments, find trending or related content, or when the user mentions 'YouTube data', 'video stats', 'transcript', or 'channel info'.
Didn't find tool you were looking for?