Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

social-media-commander社交媒体指挥官

Agent Skill

social-media-commander 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,940

周安装

125

GitHub Stars

1

下载量

1,030
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:social-media-commander(社交媒体指挥官)
来源仓库:https://github.com/cyber-bye/social-media-commander
安装命令:
openclaw skills install social-media-commander
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install social-media-commander

简介

全栈式社媒管理工具,涵盖创作、审核、发布与分析全流程。

  • 适合需要一体化解决方案的中大型运营团队使用。
  • 输入任务指令后可自动完成内容生产到数据分析闭环。
  • 复杂操作建议分步执行,避免单次请求超时失败。
  • social-media-commander 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
social-media-commander
description
Full-stack social media management skill. Covers content creation, review, scheduling, publishing, funnel management, analytics, audience insights, competitor tracking, engagement, brand voice, A/B testing, campaign management, and growth strategy. A to Z.
version
1.0.0
metadata
{"openclaw": {"emoji": "📱", "requires": {"bins": []}}}

Social Media Commander

Purpose

Agent manages the workspace owner's entire social media presence. From raw idea → polished content → scheduled post → published → analysed → improved. Every platform. Every funnel stage. Every format.


Supported Platforms

PlatformContent TypesPrimary Use
instagramFeed post, Reel, Story, Carousel, GuideVisual brand, engagement
twitter-xTweet, Thread, SpaceThought leadership, real-time
linkedinPost, Article, Newsletter, Poll, DocumentB2B, professional authority
youtubeLong-form, Shorts, Community postDeep content, SEO
threadsText post, Image postCasual, conversation
whatsapp-channelBroadcast message, PollDirect audience
telegramPost, Poll, FileCommunity, power users

Content States

StateMeaning
ideaRaw concept, not yet developed
draftBeing written/designed
reviewSubmitted for review
approvedReady to schedule
scheduledQueued with date/time
publishedLive on platform
archivedNo longer active
rejectedNot approved — reason logged

Content Types

TypeDescription
educationalTeaches something — tips, how-tos, explainers
entertainingHumor, relatable, storytelling
inspirationalMotivational, aspirational, transformation
promotionalProduct/service, offer, CTA
engagementQuestions, polls, challenges, UGC prompts
social-proofTestimonials, case studies, results
behind-scenesProcess, culture, personal
newsIndustry updates, hot takes, trends
repurposedExisting content adapted for platform

Funnel Stages

StageGoalContent Focus
awarenessNew people discover youEducational, entertaining, viral
considerationFollowers evaluate your valueSocial proof, deep value, FAQs
conversionAudience becomes customersPromotional, offers, urgency
retentionCustomers stay and returnBehind-scenes, loyalty, community
advocacyCustomers become promotersUGC, referral, ambassador

Every piece of content must be tagged with a funnel stage.


Content Pillars

Defined in brand/guidelines/pillars.md. Every post must align with at least one pillar. Default pillars (customizable):

  1. Education / Value
  2. Authority / Expertise
  3. Personality / Story
  4. Community / Engagement
  5. Promotion / Conversion

The Content Engine (idea → published)

IDEA captured
    ↓
DEVELOP: format, platform, angle, hook
    ↓
DRAFT: write copy, define visual, add CTA
    ↓
REVIEW: brand voice check, rule compliance, funnel fit
    ↓
APPROVED → SCHEDULE (date + time + platform)
    ↓
PUBLISH (manual or via integration)
    ↓
TRACK: engagement metrics at 1h / 24h / 7d
    ↓
ANALYSE: what worked, what didn't
    ↓
IMPROVE: update templates, adjust strategy

Slug Format

Content: YYYY-MM-DD-<platform>-<type>-<3-word-desc> Campaign: <name>-<YYYY-MM> Competitor: <brand-name>-analysis


Folder Structure

social-media-commander/
  platforms/<platform>/
    profile.md         ← account info, bio, links, stats
    strategy.md        ← platform-specific strategy
    best-times.md      ← optimal posting times
    performance.md     ← running metrics log

  content/
    drafts/            ← state: idea / draft
      <slug>/content.md
    scheduled/         ← state: scheduled
    published/         ← state: published (with metrics)
    archived/
    templates/         ← reusable content templates
    assets-index.md    ← index of visual assets (no files stored)

  calendar/
    YYYY-MM.md         ← monthly content calendar

  funnels/
    <stage>/
      strategy.md      ← how we approach this stage
      content-index.md ← all content at this stage

  campaigns/
    active/<campaign-id>/
      manifest.md      ← goal, budget, timeline, content list
      performance.md   ← real-time results
    completed/
    templates/

  analytics/
    daily/YYYY-MM-DD.md
    weekly/YYYY-WNN.md
    monthly/YYYY-MM.md
    reports/           ← deep analysis reports

  audience/
    segments/          ← audience segment definitions
    personas/          ← buyer personas
    competitors/       ← competitor analysis entries

  engagement/
    comments/          ← comments requiring response
    dms/               ← DMs to track
    mentions/          ← brand mentions
    saved/             ← notable engagement to reference

  brand/
    voice/guidelines.md     ← tone, language, personality
    guidelines/
      pillars.md       ← content pillars
      dos-donts.md     ← brand-level rules
      visual.md        ← visual identity guidance
    hashtags/
      master.md        ← all hashtags by category
      performance.md   ← which hashtags work
    hooks/
      master.md        ← proven hook formulas
      performance.md   ← which hooks perform

  hooks/               ← skill execution hooks
  workflows/           ← process definitions
  rules/do/ rules/dont/ rules/platform-specific/
  reviews/pending/ approved/ rejected/
  memory/schema.json index.json
  crons/active/ completed/
  templates/
  CONTENT_LOG.md       ← append-only publish log
  ANALYTICS_SUMMARY.md ← running performance snapshot
  GROWTH_JOURNAL.md    ← weekly growth reflections
  STATS.md
  SOUL.md
  AGENT.md

A/B Testing

When testing content variants:

  1. Create two entries with same concept, different angle/hook/format
  2. Tag both: ab_test: true, ab_group: A / ab_group: B
  3. After 7 days: compare metrics, declare winner
  4. Log winner in brand/hooks/performance.md and templates

Repurposing Engine

Every published piece of long-form content should be repurposed:

SourceRepurpose into
YouTube videoShorts, LinkedIn post, Twitter thread, Instagram carousel
Blog/articleLinkedIn article, Twitter thread, Instagram carousel, Reels script
PodcastAudiogram, quote cards, Twitter thread
Twitter threadLinkedIn post, Instagram carousel

Tag repurposed content: repurposed_from: <original-slug>


Crisis Protocol

If negative viral content / PR issue:

  1. Capture in engagement/mentions/ with tag crisis: true
  2. Immediate advisory to owner
  3. Pause all scheduled promotional content
  4. Draft response per brand/voice/guidelines.md
  5. Owner approves before any response goes live
  6. Log in CONTENT_LOG.md with crisis: resolved

Competitor Tracking

For each tracked competitor in audience/competitors/:

  • Platform presence and frequency
  • Content types they use
  • Engagement rates (estimated)
  • What's working for them
  • Gaps we can exploit
  • Monthly update schedule

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

90.38%
按下载量换算931

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills