social-media
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.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- social-media
- tags
- [ "writing", "marketing", "social", "content" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- 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.
03 SKILL.md 正文
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.
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.