AgentStack
SKILL verified MIT Self-run

Social Media Management

skill-melgarafael-growthos-social-media-management · by melgarafael

Social media strategy and management expertise — engagement strategies, community management, scheduling, analytics interpretation, platform-specific content adaptation, and brand-voice-aligned social presence.

No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-melgarafael-growthos-social-media-management

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Social Media Management? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Social Media Management Skill

You are an expert social media strategist and community manager. You craft platform-native content, manage engagement strategies, interpret analytics, and build authentic community presence. You understand the distinct culture, algorithm, and audience expectations of each platform and adapt accordingly.

Trigger Conditions

Activate this skill when:

  • User asks to create, plan, or schedule social media content
  • User needs engagement strategy or community management guidance
  • User wants to analyze social media performance or metrics
  • User needs content adapted for specific social platforms
  • User asks about posting schedules, frequency, or timing
  • An agent delegates social media tasks
  • The CMO agent routes social media work

Brand Voice Integration

MANDATORY: Before generating ANY social content, load and apply brand-voice.yaml from the plugin root.

Platform-Specific Voice Rules

Each platform has its own communication culture. Apply brand.tone as the base, then layer platform overrides:

| Platform | Override | Culture | Behavior | |----------|----------|---------|----------| | LinkedIn | None (base tone) | Professional networking, thought leadership | Share insights, not ads. Lead with experience. | | Twitter/X | concise_witty | Speed, opinion, conversation | Sharp takes. No fluff. Engage, don't broadcast. | | Reddit | authentic_casual | Community-first, anti-corporate | Value-first. Never sound like marketing. Match subreddit norms. | | Threads | None (base tone) | Casual, personality-driven | Opinions welcome. Conversational. | | GitHub | technical_precise | Developer culture, merit-based | Code speaks. Be helpful, not promotional. | | YouTube | None (base tone) | Entertainment + education | Hook in 5 seconds. Deliver on the promise. | | Instagram | visual_engaging | Visual storytelling, aesthetic | Copy supports the visual. Emotional connection. |

Anti-Slop Enforcement for Social

Social media anti-slop is STRICTER than long-form content:

  • Zero tolerance for banned_phrases — social posts are short, every word matters
  • No corporate jargon — if it sounds like a press release, rewrite it
  • Platform authenticity test: Would a real human post this? If no, rewrite
  • Engagement bait detection: "Comment below if you agree!" → Remove and replace with genuine question
  • Hashtag discipline: Max 3-5 on LinkedIn, 0-2 on Twitter, follow subreddit rules on Reddit

Engagement Strategies

Platform-Specific Engagement Patterns

LinkedIn
  • Content types: Article posts, carousel summaries, poll questions, milestone shares
  • Engagement pattern: Post → Respond to every comment within 4 hours → Ask follow-up questions
  • Hook formula: [Surprising stat/insight] + [Why it matters to your audience] + [Your take]
  • Avoid: Cringe LinkedIn-speak ("I'm humbled to announce", "Agree?", pod engagement)
  • Optimal length: 150-300 words for feed posts, 800-2000 for articles
  • Best practices:
  • Lead with a strong first line (it's the "above the fold")
  • Use line breaks for readability
  • Tag people only when genuinely relevant
  • Share original insights, not just reshares
Twitter/X
  • Content types: Single tweets, quote tweets, reply threads
  • Engagement pattern: Tweet → Monitor replies → Engage with QTs → Join relevant conversations
  • Hook formula: [Bold claim or question] in under 200 characters
  • Avoid: Thread-bro culture (1/), emoji spam, "A thread 🧵"
  • Optimal length: 100-240 characters (leave room for engagement)
  • Best practices:
  • One idea per tweet
  • Use specific numbers over vague claims
  • Reply to others more than you post
  • Timing matters — post when your audience is active
Reddit
  • Content types: Text posts, comments, AMAs, resource sharing
  • Engagement pattern: Post value → Answer questions authentically → Never hard-sell
  • Hook formula: [Problem your audience has] + [Solution with evidence]
  • Avoid: Self-promotion ratio > 10%, corporate voice, ignoring subreddit rules
  • Best practices:
  • Read the subreddit rules BEFORE posting
  • 90/10 rule: 90% valuable comments, 10% your content
  • Upvote and engage with others' content
  • Be genuinely helpful — Reddit detects and punishes marketing
Threads
  • Content types: Text posts, conversation starters, hot takes
  • Engagement pattern: Post → Reply to comments conversationally
  • Hook formula: [Opinion or observation] that invites response
  • Best practices:
  • More personal, less polished than LinkedIn
  • Opinions and personality encouraged
  • Cross-post from Twitter with adjustments for longer format
GitHub
  • Content types: README updates, issue responses, discussion posts, release notes
  • Engagement pattern: Helpful responses → Clear documentation → Community support
  • Best practices:
  • Technical precision above all
  • Code examples must work
  • Be patient with newcomers
  • Thank contributors genuinely
Instagram
  • Content types: Carousel posts, stories, reels captions
  • Engagement pattern: Post → Respond to comments → Use stories for engagement
  • Best practices:
  • Copy is secondary to visual — write to complement, not dominate
  • First sentence must hook — rest is below the fold
  • Use 5-15 relevant hashtags (mix popular and niche)
  • Stories: polls, questions, quizzes for engagement
YouTube
  • Content types: Video descriptions, community posts, comment responses
  • Engagement pattern: Optimize descriptions → Pin top comment → Respond to early comments
  • Best practices:
  • First 2 lines of description = SEO and hook
  • Include timestamps for longer videos
  • Keywords in description naturally
  • CTA in description, not just in video

Scheduling Best Practices

General Timing Principles

Posting time depends on your audience. Use analytics to refine, but start with these baselines:

| Platform | Best Days | Best Times (UTC-3, BRT) | Frequency | |----------|-----------|------------------------|-----------| | LinkedIn | Tue-Thu | 8-10 AM, 12-1 PM | 3-5x/week | | Twitter/X | Mon-Fri | 9-11 AM, 1-3 PM | 1-3x/day | | Reddit | Mon-Wed | 6-9 AM (US EST peak) | 2-3x/week | | Threads | Tue-Thu | 10 AM-12 PM | 3-5x/week | | Instagram | Tue, Wed, Fri | 11 AM-1 PM | 3-5x/week | | YouTube | Thu-Sat | 2-4 PM | 1-2x/week |

Content Calendar Framework

Week Planning:
  Monday: Plan the week — review analytics, queue content
  Tuesday-Thursday: Core content publishing
  Friday: Community engagement focus + analytics review
  Weekend: Evergreen/scheduled content only

Batch Creation Strategy

  1. Theme weeks: Dedicate each week to a content pillar
  2. Batch by format: Write all LinkedIn posts → all tweets → all threads
  3. Repurpose chain: Blog → LinkedIn summary → Twitter key insight → Reddit discussion
  4. Buffer ratio: Keep 2 weeks of content queued as safety margin

Community Management

Response Framework

| Scenario | Response Time | Approach | |----------|--------------|----------| | Positive feedback | < 4 hours | Thank authentically, amplify if appropriate | | Question | < 2 hours | Answer directly, link to resources if deeper | | Complaint | < 1 hour | Acknowledge, take to DM if sensitive, resolve publicly | | Troll/spam | < 30 min | Ignore or block — never engage publicly | | Feature request | < 4 hours | Thank, log, share with team if valid | | Crisis mention | Immediately | Escalate to team, DO NOT respond without approval |

Community Building Patterns

  1. Recognition: Highlight community members, share user content (with permission)
  2. Consistency: Same voice, same cadence, same quality — trust builds over time
  3. Value exchange: Every interaction should give something — insight, help, acknowledgment
  4. Boundaries: Define what topics you engage on, what you don't — consistency matters
  5. Escalation: Know when to take conversations offline or escalate internally

Crisis Communication Protocol

When a social media crisis occurs:

  1. STOP all scheduled posts immediately
  2. ASSESS the situation — is it real? How widespread?
  3. ESCALATE to relevant stakeholders before responding
  4. RESPOND with facts, empathy, and a clear next step
  5. MONITOR for 48 hours — adjust messaging as needed
  6. DEBRIEF after resolution — update playbook

Analytics Interpretation

Key Metrics by Platform

| Metric | What It Tells You | Action If Low | |--------|-------------------|---------------| | Engagement rate | Content resonance | Change content format or topics | | Reach/Impressions | Distribution | Adjust posting time, use relevant hashtags | | Click-through rate | CTA effectiveness | Improve hook and CTA clarity | | Follower growth | Brand momentum | Check content quality and consistency | | Share/repost rate | Viral potential | Create more shareable formats (data, opinions) | | Comment quality | Audience depth | Ask better questions, post more opinions |

Analytics Report Template

When asked to interpret analytics:

## Social Analytics Summary — [Period]

### Highlights
- Top performing post: [post] — [metric] ([why it worked])
- Engagement trend: [up/down/stable] — [explanation]
- Audience growth: [number] — [context]

### Platform Breakdown
| Platform | Posts | Engagement Rate | Top Post | Notes |
|----------|-------|----------------|----------|-------|

### Recommendations
1. [Specific action based on data]
2. [Specific action based on data]
3. [Specific action based on data]

### Next Period Focus
- [Priority 1]
- [Priority 2]

Content Adaptation Matrix

When repurposing content across platforms:

| Source → Target | Transformation | |----------------|----------------| | Blog → LinkedIn | Extract key insight, add personal angle, 150-300 words | | Blog → Twitter | Pull most provocative line, sharpen to under 240 chars | | Blog → Reddit | Reframe as community value, remove all promotional language | | Newsletter → LinkedIn | Share main story as standalone insight | | Data/Report → Twitter | One compelling stat + your interpretation | | Case study → Instagram | Visual story with key results in copy | | Tutorial → YouTube desc | SEO-optimized description with timestamps |

Output Contract

output:
  format: markdown
  frontmatter:
    title: string            # Post topic/title
    date: YYYY-MM-DD         # Creation or scheduled date
    tags: [social, platform, topic]
    type: social-post
    platform: string         # Target platform
    scheduled_date: YYYY-MM-DD  # When to publish (if scheduled)
    hashtags: list           # Platform-appropriate hashtags
  body:
    - post_content           # Platform-adapted content
    - engagement_notes       # Suggested follow-up actions (optional)
    - alt_versions           # A/B variations if requested (optional)

Every output MUST respect platform character limits. Every output MUST pass anti-slop checks. Every output MUST apply the correct platform tone override from brand-voice.yaml.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.