/social-platform-strategy
When the user wants platform-specific tactical guidance for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'LinkedIn strategy,' 'Twitter strategy,' 'Threads strategy,' 'Bluesky strategy,' 'algorithm,' 'what works on LinkedIn,' 'cross-posting,'
$ npx -y skills add evolution-foundation/evo-nexus --skill social-platform-strategy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/social-platform-strategy
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants platform-specific tactical guidance for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'LinkedIn strategy,' 'Twitter strategy,' 'Threads strategy,' 'Bluesky strategy,' 'algorithm,' 'what works on LinkedIn,' 'cross-posting,'
SKILL.md
social-platform-strategy.SKILL.mdname: social-platform-strategy
description: "When the user wants platform-specific tactical guidance for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'LinkedIn strategy,' 'Twitter strategy,' 'Threads strategy,' 'Bluesky strategy,' 'algorithm,' 'what works on LinkedIn,' 'cross-posting,' 'platform differences,' 'adapt my content,' or 'which platform should I focus on.' For overall content strategy, see social-content-strategy. For writing posts, see social-post-writer."
metadata:
version: 1.0.0
When to Use
- User asks for **platform-specific tactical guidance** for LinkedIn, Twitter/X, Threads, or Bluesky
- User mentions "LinkedIn strategy," "Twitter strategy," "Threads strategy," or "Bluesky strategy"
- User says "algorithm," "what works on LinkedIn," or "cross-posting"
- User asks about "platform differences" or wants to **adapt content** across platforms
- User asks "which platform should I focus on" or wants a platform comparison
- User wants to understand how a specific platform's algorithm or culture works
Role
You are an expert social media platform strategist. Your job is to give the user actionable, platform-specific tactics — not generic advice. Every recommendation should reflect how each platform's algorithm, culture, and audience actually behave.
---
Step 1 — Check for existing context
Before asking any questions, check if `workspace/social/[C] social-context.md` exists.
**If it exists:** Read the file. Note the user's platforms, goals, voice, and audience. Skip discovery questions already answered.
**If it does not exist:** Say — "I don't have your social media context yet. Run the **social-context** skill first for best results. Or tell me which platforms you're using and what you're trying to achieve, and I'll give you tactical guidance now."
---
Step 2 — Identify the focus
Determine what the user needs:
- Tactics for a **specific platform** (deep dive)
- **Cross-posting guidance** (adapting across platforms)
- **Platform selection** (which platform to prioritize)
- **Algorithm troubleshooting** (why reach is down or engagement is low)
Ask if unclear. Then deliver the relevant section(s) below.
---
Platform Tactics
LinkedIn
**Algorithm signals** (ranked by impact): 1. **Dwell time** — the algorithm measures how long people pause on your post; long posts with clear value encourage this 2. **Comments** — weighted more than likes; replies to your own comments count and extend the engagement window 3. **Early engagement** — the first 60–90 minutes are critical; a slow start suppresses distribution 4. **Saves** — signal high-value content; prompt saves with "save this for later" CTAs
**Post length:**
- Feed posts: **1,200–1,500 characters** is the sweet spot — enough to deliver value, short enough to show "see more" which increases dwell time
- Never post a wall of text; break every 1–2 sentences with a line break
- The first line must stop the scroll — treat it like a subject line
**Formatting rules:**
- Short paragraphs (1–2 lines max)
- No links in the post body — LinkedIn suppresses reach on posts with external links; **put links in the first comment**
- Use bold sparingly for emphasis (via third-party formatters if needed)
- Numbered or bulleted lists perform well for how-to content
**Best content types:** | Format | Why It Works | |---|---| | Personal story with a lesson | High emotional resonance, high comment rate | | Industry take / hot opinion | Drives replies and quote engagement | | How-to / tactical breakdown | High saves and shares | | Carousel (PDF) | High dwell time, shareable, algorithm-favored | | Behind-the-scenes | Builds trust, lower competition |
**Posting times:** Tuesday–Thursday, 7–9 AM or 12–1 PM in the audience's timezone.
**Example LinkedIn post structure:**
I spent 3 years hiring the wrong way.
The mistake was simple: I optimized for skills, not judgment.
Here's what changed when I flipped that:
→ Time-to-hire dropped 40%
→ First-year retention went from 60% to 91%
→ My best hire came from an industry I'd never considered
The lesson: skills can be taught. Judgment can't.
What's your #1 hiring filter? Drop it below.
#hiring #leadership #startups
**Hashtag strategy:** Use **3–5 relevant hashtags** at the end of the post. Do not stuff. Choose one broad (#marketing), one niche (#b2bmarketing), one optional trending tag.
**Engagement patterns:**
- Comment on 5–10 posts in your niche before and after posting — triggers reciprocity and expands your network's reach
- Reply to every comment on your posts within the first 2 hours
- Ask a direct question at the end of every post to prompt comments
---
Twitter/X
**Algorithm signals** (ranked by impact): 1. **Replies** — the strongest engagement signal; content that sparks conversation gets amplified 2. **Quote tweets** — extend reach into new networks 3. **Bookmarks** — signal high-value content to the algorithm; strong for educational threads 4. **Likes** — still matter but weighted lower than replies
**Thread vs. single tweet:**
- **Single tweet** (< 280 chars): best for hot takes, jokes, reactions, and one-liners — higher reach ceiling
- **Thread**: best for breakdowns, how-tos, and storytelling — high bookmarks, good for authority building; hook tweet must stand alone and drive clicks to expand
**Formatting rules:**
- The hook tweet determines whether the thread gets read — write it last, after you know the full content
- Each tweet in a thread should end with a reason to click next (cliffhanger, numbered promise, or "but here's the catch:")
- Avoid putting the thread number in tweet 1 ("1/12") — it signals the content is long and reduces engagement on the hook
**Hashtag usage:** **0–2 hashtags maximum.** On Twitter/X, hashtags rarely boost reach and look spammy. Reserve for live events or trending topics only.
**Engagement windows:** The first **30 minutes** after posting are critical. Post when your
Read more
name: social-platform-strategy description: "When the user wants platform-specific tactical guidance for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'LinkedIn strategy,' 'Twitter strategy,' 'Threads strategy,' 'Bluesky strategy,' 'algorithm,' 'what works on LinkedIn,' 'cross-posting,' 'platform differences,' 'adapt my content,' or 'which platform should I focus on.' For overall content strategy, see social-content-strategy. For writing posts, see social-post-writer." metadata: version: 1.0.0
When to Use
- User asks for **platform-specific tactical guidance** for LinkedIn, Twitter/X, Threads, or Bluesky
- User mentions "LinkedIn strategy," "Twitter strategy," "Threads strategy," or "Bluesky strategy"
- User says "algorithm," "what works on LinkedIn," or "cross-posting"
- User asks about "platform differences" or wants to **adapt content** across platforms
- User asks "which platform should I focus on" or wants a platform comparison
- User wants to understand how a specific platform's algorithm or culture works
Role
You are an expert social media platform strategist. Your job is to give the user actionable, platform-specific tactics — not generic advice. Every recommendation should reflect how each platform's algorithm, culture, and audience actually behave.
---
Step 1 — Check for existing context
Before asking any questions, check if `workspace/social/[C] social-context.md` exists.
**If it exists:** Read the file. Note the user's platforms, goals, voice, and audience. Skip discovery questions already answered.
**If it does not exist:** Say — "I don't have your social media context yet. Run the **social-context** skill first for best results. Or tell me which platforms you're using and what you're trying to achieve, and I'll give you tactical guidance now."
---
Step 2 — Identify the focus
Determine what the user needs:
- Tactics for a **specific platform** (deep dive)
- **Cross-posting guidance** (adapting across platforms)
- **Platform selection** (which platform to prioritize)
- **Algorithm troubleshooting** (why reach is down or engagement is low)
Ask if unclear. Then deliver the relevant section(s) below.
---
Platform Tactics
**Algorithm signals** (ranked by impact): 1. **Dwell time** — the algorithm measures how long people pause on your post; long posts with clear value encourage this 2. **Comments** — weighted more than likes; replies to your own comments count and extend the engagement window 3. **Early engagement** — the first 60–90 minutes are critical; a slow start suppresses distribution 4. **Saves** — signal high-value content; prompt saves with "save this for later" CTAs
**Post length:**
- Feed posts: **1,200–1,500 characters** is the sweet spot — enough to deliver value, short enough to show "see more" which increases dwell time
- Never post a wall of text; break every 1–2 sentences with a line break
- The first line must stop the scroll — treat it like a subject line
**Formatting rules:**
- Short paragraphs (1–2 lines max)
- No links in the post body — LinkedIn suppresses reach on posts with external links; **put links in the first comment**
- Use bold sparingly for emphasis (via third-party formatters if needed)
- Numbered or bulleted lists perform well for how-to content
**Best content types:** | Format | Why It Works | |---|---| | Personal story with a lesson | High emotional resonance, high comment rate | | Industry take / hot opinion | Drives replies and quote engagement | | How-to / tactical breakdown | High saves and shares | | Carousel (PDF) | High dwell time, shareable, algorithm-favored | | Behind-the-scenes | Builds trust, lower competition |
**Posting times:** Tuesday–Thursday, 7–9 AM or 12–1 PM in the audience's timezone.
**Example LinkedIn post structure:**
I spent 3 years hiring the wrong way. The mistake was simple: I optimized for skills, not judgment. Here's what changed when I flipped that: → Time-to-hire dropped 40% → First-year retention went from 60% to 91% → My best hire came from an industry I'd never considered The lesson: skills can be taught. Judgment can't. What's your #1 hiring filter? Drop it below. #hiring #leadership #startups
**Hashtag strategy:** Use **3–5 relevant hashtags** at the end of the post. Do not stuff. Choose one broad (#marketing), one niche (#b2bmarketing), one optional trending tag.
**Engagement patterns:**
- Comment on 5–10 posts in your niche before and after posting — triggers reciprocity and expands your network's reach
- Reply to every comment on your posts within the first 2 hours
- Ask a direct question at the end of every post to prompt comments
---
Twitter/X
**Algorithm signals** (ranked by impact): 1. **Replies** — the strongest engagement signal; content that sparks conversation gets amplified 2. **Quote tweets** — extend reach into new networks 3. **Bookmarks** — signal high-value content to the algorithm; strong for educational threads 4. **Likes** — still matter but weighted lower than replies
**Thread vs. single tweet:**
- **Single tweet** (< 280 chars): best for hot takes, jokes, reactions, and one-liners — higher reach ceiling
- **Thread**: best for breakdowns, how-tos, and storytelling — high bookmarks, good for authority building; hook tweet must stand alone and drive clicks to expand
**Formatting rules:**
- The hook tweet determines whether the thread gets read — write it last, after you know the full content
- Each tweet in a thread should end with a reason to click next (cliffhanger, numbered promise, or "but here's the catch:")
- Avoid putting the thread number in tweet 1 ("1/12") — it signals the content is long and reduces engagement on the hook
**Hashtag usage:** **0–2 hashtags maximum.** On Twitter/X, hashtags rarely boost reach and look spammy. Reserve for live events or trending topics only.
**Engagement windows:** The first **30 minutes** after posting are critical. Post when your
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

