Use when an org role acts as social media manager and must run a platform-native presence: per-platform content, posting cadence and fast community engagement. Covers audience-based platform choice, per-platform briefs and KPIs and conversation-driving content. Role guidance; for strategy playbooks see social-media-manager.
Installs into .claude/skills of the current project.
Are you the author of Social Media?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-social-media)
---
name: social-media
description: "Use when an org role acts as social media manager and must run a platform-native presence: per-platform content, posting cadence and fast community engagement. Covers audience-based platform choice, per-platform briefs and KPIs and conversation-driving content. Role guidance; for strategy playbooks see social-media-manager."
tags: ["writing","marketing","social","content"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Social Media — Best Practices
## Focus
Runs platform-native social presence — content, scheduling, and community engagement — tuned to each platform's format and audience rather than a single cross-posted strategy.
## Best practices
- Choose platforms based on audience research, not industry trends or personal preference.
- Give each platform its own brief, format, and KPI — a platform-native approach beats a single repurposed asset everywhere.
- Prioritize consistency of posting over raw volume; a steady cadence outperforms sporadic viral attempts long-term.
- Respond quickly to comments and DMs — response speed is itself a core driver of engagement and part of social customer service.
- Optimize for content that sparks conversation and saves, not just impressions or views.
- Let real business goals (leads, signups, retention) drive strategy, not vanity metrics alone.
- Use AI to speed up production while keeping human review — content with visible human experience and personality still outperforms generic AI output.
## Common pitfalls
- Cross-posting identical content to every platform instead of adapting tone/format per channel.
- Treating follower count or likes as success metrics disconnected from actual business outcomes.
- Slow or inconsistent response times to comments/DMs, which reads as neglect and suppresses reach.
- Publishing on a reactive, trend-chasing basis instead of a planned, consistent cadence.
## Tools & techniques
- Platform-specific content calendars with separate briefs per channel.
- Short-form vertical video prioritization (Reels/Shorts) where the algorithm rewards it, paired with native community engagement (replies, polls, comments) rather than one-way broadcasting.
- Weekly performance review against a small, fixed set of indicators per platform, with findings translated into concrete changes.
- Escalation path for negative/sensitive comments to human review before public reply.
