domains / families / marketing / social-content

social-content

combined

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see content-strategy. When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.

When to use

• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies overlap on the core social media strategy workflow (context gathering, platform selection, content pillars, and repurposing), but they disagree on the agent's capabilities and contain material steps the others lack. The LeoYeAI/openclaw-marketing-skills copy is the most complete standalone procedure, including a specific check for a product marketing context file and a detailed engagement routine. The LeoYeAI/openclaw-master-skills copy provides significantly more granular platform-specific constraints (best times, character limits, and 'what doesn't work' lists) and assumes direct access to a scheduling platform. The sickn33 copy is a wrapper that delegates to a separate guide and adds a 'critical' risk flag. Because the first copy lacks the scheduling assumption and the second lacks the context file check, crowning one would hide a real alternative procedure.