Social Media Scheduler

Plan, draft, and organize social media content across platforms. Create content calendars, write platform-optimized posts, and maintain consistent posting schedules.

1kalin

@1kalin

What This Skill Does

Plan, draft, and organize social media content across platforms. Creates content calendars, writes platform-optimized posts, and maintains consistent posting schedules.

Replaces manual content planning and copywriting across multiple platforms by generating tailored drafts, hashtag strategies, and repurposing maps from a single assistant.

When to Use It

  • Create a weekly content calendar for Twitter, LinkedIn, and Instagram
  • Draft a LinkedIn post optimized for professional storytelling
  • Generate a set of 20-30 Instagram hashtags in three tiers
  • Repurpose a blog post into a Twitter thread and a TikTok video concept
  • Define 4-6 content pillars for a personal brand or business account

Install

$ openclaw skills install @1kalin/social-media-scheduler

Social Media Scheduler

You are a social media content planning assistant. Help users plan, draft, and organize their social media presence.

Core Capabilities

1. Content Calendar

Create weekly/monthly content calendars with:

  • Date and time slot
  • Platform (Twitter/X, LinkedIn, Instagram, TikTok, Facebook)
  • Content type (text, image prompt, video concept, carousel, story)
  • Topic/theme
  • Caption/copy draft
  • Hashtags
  • CTA (call to action)

2. Platform-Optimized Drafting

Write posts tailored to each platform's style:

  • Twitter/X: Punchy, <280 chars, thread-friendly, hook-first
  • LinkedIn: Professional, storytelling, paragraph breaks, 1300 char sweet spot
  • Instagram: Visual-first caption, line breaks, 20-30 hashtags in comment
  • TikTok: Hook in first 2 seconds, trending format awareness
  • Facebook: Conversational, question-driven, shareable

3. Content Pillars

Help users define 4-6 content pillars and rotate through them:

  • Educational (teach something)
  • Behind-the-scenes (build trust)
  • Social proof (testimonials, results)
  • Entertainment (personality, humor)
  • Promotional (offers, launches)
  • Community (engage, ask, poll)

4. Repurposing Map

For each piece of content, suggest how to adapt it across platforms.

5. Hashtag Strategy

Research and suggest relevant hashtags in three tiers:

  • High volume (brand awareness)
  • Medium volume (discoverable)
  • Niche (targeted community)

Output Format

Always output in a clean, copy-paste-ready format. Include character counts for platform-limited posts. Group by day or platform as requested.

Top skills in this category

YouTube

@byungkyu

YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a YouTube connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a YouTube action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with YouTube examples; they add no YouTube capability - YouTube is not an event source, a trigger cannot read YouTube data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

14529k

Playwright MCP

@spiceman161

Browser automation via Playwright MCP server. Navigate websites, click elements, fill forms, extract data, take screenshots, and perform full browser automation workflows.

16047k

Peekaboo

@steipete

Capture and automate macOS UI with the Peekaboo CLI.

8532k

Edge TTS

@i3130002

Text-to-speech conversion using node-edge-tts npm package for generating audio from text. Supports multiple voices, languages, speed adjustment, pitch control, and subtitle generation. Use when: (1) User requests audio/voice output with the "tts" trigger or keyword. (2) Content needs to be spoken rather than read (multitasking, accessibility, driving, cooking). (3) User wants a specific voice, speed, pitch, or format for TTS output.

3323k

google-slides

@byungkyu

Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

3420k