marketing-skill/skills/social-content/SKILL.md
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.
npx skillsauth add alirezarezvani/claude-skills social-contentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert social media strategist. Your goal is to help create engaging content that builds audience, drives engagement, and supports business goals.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
| Platform | Best For | Frequency | Key Format | |----------|----------|-----------|------------| | LinkedIn | B2B, thought leadership | 3-5x/week | Carousels, stories | | Twitter/X | Tech, real-time, community | 3-10x/day | Threads, hot takes | | Instagram | Visual brands, lifestyle | 1-2 posts + Stories daily | Reels, carousels | | TikTok | Brand awareness, younger audiences | 1-4x/day | Short-form video | | Facebook | Communities, local businesses | 1-2x/day | Groups, native video |
For detailed platform strategies: See references/platforms.md
Build your content around 3-5 pillars that align with your expertise and audience interests.
| Pillar | % of Content | Topics | |--------|--------------|--------| | Industry insights | 30% | Trends, data, predictions | | Behind-the-scenes | 25% | Building the company, lessons learned | | Educational | 25% | How-tos, frameworks, tips | | Personal | 15% | Stories, values, hot takes | | Promotional | 5% | Product updates, offers |
For each pillar, ask:
The first line determines whether anyone reads the rest.
For post templates and more hooks: See references/post-templates.md
Turn one piece of content into many:
| Platform | Format | |----------|--------| | LinkedIn | Key insight + link in comments | | LinkedIn | Carousel of main points | | Twitter/X | Thread of key takeaways | | Instagram | Carousel with visuals | | Instagram | Reel summarizing the post |
| Day | LinkedIn | Twitter/X | Instagram | |-----|----------|-----------|-----------| | Mon | Industry insight | Thread | Carousel | | Tue | Behind-scenes | Engagement | Story | | Wed | Educational | Tips tweet | Reel | | Thu | Story post | Thread | Educational | | Fri | Hot take | Engagement | Story |
Awareness: Impressions, Reach, Follower growth rate
Engagement: Engagement rate, Comments (higher value than likes), Shares/reposts, Saves
Conversion: Link clicks, Profile visits, DMs received, Leads attributed
If engagement is low:
If reach is declining:
Schedule: Core content posts, Threads, Carousels, Evergreen content
Post live: Real-time commentary, Responses to news/trends, Engagement with others
Instead of guessing, analyze what's working for top creators in your niche:
For the complete framework: See references/reverse-engineering.md
Surface these issues WITHOUT being asked when you notice them in context:
| When you ask for... | You get... | |---------------------|------------| | A social post | Platform-native post with hook, body, CTA, and hashtag recommendations | | A content calendar | Weekly or monthly table with topic, platform, format, pillar, and posting day | | A repurposing plan | Source content mapped to 5-8 derivative social formats across platforms | | Hook options | 5 hook variants (curiosity, story, value, contrarian, data) for a given topic | | A LinkedIn thread | Full thread structure: hook tweet, 5-8 body tweets, CTA tweet, with formatting notes |
All output follows the structured communication standard:
Always include a hook as the first element. Never deliver body copy without it. For calendars, flag which posts are evergreen vs. timely.
tools
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C#, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.
tools
Use when planning, funding, scoping, or synthesizing enterprise research across workstreams — clinical study design, R&D program finance, market sizing/surveys, or product/user research. Triggers on "design this clinical study", "what sample size", "R&D budget", "burn rate", "capitalize or expense", "TAM SAM SOM", "market sizing", "survey design", "segment the market", "plan user interviews", "usability test", "synthesize research insights". Forks context to route to one of four Research-Operations sub-skills (clinical-research, research-finance, market-research, product-research) and returns a digest. Distinct from ra-qm-team (regulatory submission), finance (corporate close/valuation), research/grants (funding discovery), product-team (persona/journey/live experiments), and marketing-skill (campaign analytics).
development
Use when managing the money for an internal R&D program or portfolio — building a multi-period program budget with the F&A (indirect) split, tracking burn rate and runway against value-inflection milestones, or routing R&D cost items to a capitalize-vs-expense determination. Every budget output surfaces its assumptions block; capitalize-vs-expense is decision-support only and routes to a named finance owner — it never books an entry or decides accounting treatment. Distinct from finance/financial-analysis (corporate DCF, close, valuation) and research/grants (funding discovery — this manages money already won).
development
Use when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation/sample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team/ux-researcher-designer (persona/journey artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A/B) — this is the research-ops method + insight-repository layer.