Skill 详情
platform-strategy-sms
Provides platform-specific social strategy and tactics.
使用前先检查
自动化审核只检查相关性,不代表安全审查或推荐。使用前请阅读来源中的说明。
SKILL.md
这段内容是审核时保存的快照。外部来源才是完整且最新的版本。
--- name: platform-strategy-sms 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 content-strategy-sms. For writing posts, see post-writer-sms." 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 `.agents/social-media-context-sms.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-media-context-sms** 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在 GitHub 阅读完整来源 (打开外部页面)