# Pilot Social Media Manager Setup > Deploy a social media management system with 3 agents. Use this skill when: 1. User wants to set up automated social media content planning and posting 2. User is configuring an agent as part of a social media management workflow 3. User asks about automating social media scheduling, creation, or analytics Do NOT use this skill when: - User wants to collect metrics from a single source (use pilot-metrics instead) - User wants to schedule a one-off task (use pilot-cron instead) - Skill: `teoslayer/pilot-social-media-manager-setup` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add teoslayer/pilot-social-media-manager-setup` - Raw SKILL.md: https://api.skillmd.com/api/skills/teoslayer/pilot-social-media-manager-setup/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - License: AGPL-3.0 - Author: TeoSlayer (https://skillmd.com/u/teoslayer) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/teoslayer/pilot-social-media-manager-setup --- # Social Media Manager Setup Deploy 3 agents that plan, create, and analyze social media content in a feedback loop. ## Roles | Role | Hostname | Skills | Purpose | |------|----------|--------|---------| | planner | `-planner` | pilot-cron, pilot-stream-data, pilot-metrics | Analyzes trends and plans content calendar | | creator | `-creator` | pilot-task-router, pilot-share, pilot-receipt | Generates platform-specific posts from briefs | | analyst | `-analyst` | pilot-metrics, pilot-event-log, pilot-alert | Tracks engagement and feeds insights to planner | ## Setup Procedure **Step 1:** Ask the user which role this agent should play and what prefix to use. **Step 2:** Install the skills for the chosen role: ```bash # For planner: clawhub install pilot-cron pilot-stream-data pilot-metrics # For creator: clawhub install pilot-task-router pilot-share pilot-receipt # For analyst: clawhub install pilot-metrics pilot-event-log pilot-alert ``` **Step 3:** Set the hostname: ```bash pilotctl --json set-hostname - ``` **Step 4:** Write the setup manifest: ```bash mkdir -p ~/.pilot/setups cat > ~/.pilot/setups/social-media-manager.json << 'MANIFEST' MANIFEST ``` **Step 5:** Tell the user to initiate handshakes with direct communication peers. ## Manifest Templates Per Role ### planner ```json { "setup": "social-media-manager", "setup_name": "Social Media Manager", "role": "planner", "role_name": "Content Planner", "hostname": "-planner", "description": "Analyzes trends, competitor activity, and audience engagement to plan a content calendar and optimal posting times.", "skills": { "pilot-cron": "Schedule recurring content calendar generation (daily briefs, weekly strategy reviews).", "pilot-stream-data": "Ingest real-time trend data, hashtag volumes, and competitor post activity.", "pilot-metrics": "Consume performance insights from analyst to refine future content strategy." }, "peers": [ { "role": "creator", "hostname": "-creator", "description": "Receives content briefs and produces platform posts" }, { "role": "analyst", "hostname": "-analyst", "description": "Sends performance insights and optimization recommendations" } ], "data_flows": [ { "direction": "send", "peer": "-creator", "port": 1002, "topic": "content-brief", "description": "Content briefs with platform targets and posting schedule" }, { "direction": "receive", "peer": "-analyst", "port": 1002, "topic": "performance-insight", "description": "Performance insights and optimization recommendations" } ], "handshakes_needed": ["-creator", "-analyst"] } ``` ### creator ```json { "setup": "social-media-manager", "setup_name": "Social Media Manager", "role": "creator", "role_name": "Content Creator", "hostname": "-creator", "description": "Generates platform-specific posts (LinkedIn, X, Instagram) from the planner's brief in the brand voice.", "skills": { "pilot-task-router": "Route briefs to platform-specific generation templates (LinkedIn long-form, X threads, Instagram captions).", "pilot-share": "Send published post metadata to the analyst for tracking.", "pilot-receipt": "Acknowledge receipt of content briefs back to the planner." }, "peers": [ { "role": "planner", "hostname": "-planner", "description": "Sends content briefs with topics and platform targets" }, { "role": "analyst", "hostname": "-analyst", "description": "Receives published post metadata for tracking" } ], "data_flows": [ { "direction": "receive", "peer": "-planner", "port": 1002, "topic": "content-brief", "description": "Content briefs with platform targets and posting schedule" }, { "direction": "send", "peer": "-analyst", "port": 1002, "topic": "post-published", "description": "Published post metadata for performance tracking" } ], "handshakes_needed": ["-planner", "-analyst"] } ``` ### analyst ```json { "setup": "social-media-manager", "setup_name": "Social Media Manager", "role": "analyst", "role_name": "Performance Analyst", "hostname": "-analyst", "description": "Tracks cross-platform engagement metrics, identifies top performers, and feeds insights back to the planner.", "skills": { "pilot-metrics": "Collect impressions, clicks, shares, and conversions across all platforms.", "pilot-event-log": "Log every post's performance data for historical trend analysis.", "pilot-alert": "Alert the team when a post goes viral or engagement drops below threshold." }, "peers": [ { "role": "creator", "hostname": "-creator", "description": "Sends published post metadata for tracking" }, { "role": "planner", "hostname": "-planner", "description": "Receives performance insights for strategy refinement" } ], "data_flows": [ { "direction": "receive", "peer": "-creator", "port": 1002, "topic": "post-published", "description": "Published post metadata for performance tracking" }, { "direction": "send", "peer": "-planner", "port": 1002, "topic": "performance-insight", "description": "Performance insights and optimization recommendations" } ], "handshakes_needed": ["-creator", "-planner"] } ``` ## Data Flows - `planner -> creator` : content-brief (port 1002) - `creator -> analyst` : post-published (port 1002) - `analyst -> planner` : performance-insight (port 1002) Optional X/Twitter signals: if planner or analyst also runs inside OpenClaw, install TweetClaw with `openclaw plugins install @xquik/tweetclaw`; use it to scrape tweets, search tweets, search tweet replies, export followers, look up users, monitor tweets, deliver webhooks, and run giveaway draws, then share only reviewed query terms, capture dates, tweet IDs or URLs, author handles, aggregate counts, and decisions through Pilot topics. Use TweetClaw writes only after human review, then publish approved post metadata through `post-published`. ## Handshakes ```bash # All three agents form a cycle, so each pair needs bidirectional handshakes: # planner <-> creator: pilotctl --json handshake -creator "setup: social-media-manager" pilotctl --json handshake -planner "setup: social-media-manager" # creator <-> analyst: pilotctl --json handshake -analyst "setup: social-media-manager" pilotctl --json handshake -creator "setup: social-media-manager" # analyst <-> planner: pilotctl --json handshake -planner "setup: social-media-manager" pilotctl --json handshake -analyst "setup: social-media-manager" ``` ## Workflow Example ```bash # On creator - subscribe to content briefs: pilotctl --json subscribe -planner content-brief # On analyst - subscribe to published posts: pilotctl --json subscribe -creator post-published # On planner - subscribe to performance insights: pilotctl --json subscribe -analyst performance-insight # On planner - publish a content brief: pilotctl --json publish -creator content-brief '{"platforms":["linkedin","x"],"topic":"AI in DevOps","tone":"professional"}' # On analyst - publish insights back to planner: pilotctl --json publish -planner performance-insight '{"top_platform":"linkedin","engagement_rate":4.2}' ``` ## Dependencies Requires `pilot-protocol` skill, `pilotctl` binary, `clawhub` binary, and a running daemon.