| name | social-strategist |
| description | Creates 30-day social media calendar with content mix, posting times, engagement hooks, and analytics targets. Integrated with messaging pillars. Returns calendar, copy templates, and posting schedule. |
| allowed-tools | Read, Write |
| effort | medium |
Social Strategist
When to activate
Monthly, at the start of campaign planning. You have messaging pillars and content pieces drafted. This skill designs a 30-day social calendar that distributes content across channels (LinkedIn, Twitter, etc.) with optimal timing, format mix, and engagement hooks. Returns ready-to-publish calendar and templates.
When NOT to use
Not for real-time social listening or crisis response — use Brand Monitor. Not for individual post creation — use Content Generator. Not without messaging pillars established.
Calendar Design Principles
Content Mix
- 40% thought leadership (your pillars and insights)
- 30% customer proof (quotes, case studies, wins)
- 20% industry insights (trends, data, research)
- 10% community engagement (retweets, replies, asks)
Posting Frequency
- LinkedIn: 3–4 times per week
- Twitter: Daily
- Instagram (if applicable): 3 times per week
Optimal Posting Times
- LinkedIn: Tuesday–Thursday, 8–10 AM or 5–7 PM
- Twitter: Varies by audience; test and adjust
- Email: Tuesday–Thursday, 10 AM or 2 PM
Engagement Mechanics
- Hook (first line): debate-friendly take or surprising fact
- Body: context, data, or story
- CTA: question, poll, or retweet request
Calendar Template
# 30-Day Social Calendar
**Month:** [Month Year]
**Platforms:** [LinkedIn, Twitter, Instagram]
**Key Themes:** [Pillar 1, Pillar 2, Pillar 3]
---
## Week 1
### Monday
- **Platform:** LinkedIn
- **Pillar:** [Pillar Name]
- **Hook:** [First line that grabs attention]
- **Body:** [Main message + proof]
- **CTA:** [Question or engagement hook]
- **Engagement Target:** X comments, Y shares
---
### Tuesday
[Same format]
---
### Wednesday
[Same format]
---
[Continue through Sunday]
---
## Week 2
[Same structure]
---
## Analytics Targets
- **Reach:** X impressions per post (or Y% growth)
- **Engagement:** Z% CTR, X% share rate
- **Comments:** Target quality over quantity (discussion vs. spam)
- **Follower Growth:** X new followers per week
- **Traffic Driven:** X clicks to website per week
---
## Copy Templates
### LinkedIn Post Template
[Hook — surprising stat or question]
[Story or insight — 3–4 sentences with context]
[Proof — customer quote, case study reference, or data]
[CTA — question or discussion invite]
### Twitter Template
[Hook + main insight — 280 characters max]
[Reply 1: Context or data]
[Reply 2: Customer proof or link]
---
## Hashtag Strategy
Do NOT overuse. Max 2–3 per LinkedIn post, 1–2 per tweet.
- [Industry hashtag]: #[example]
- [Brand hashtag]: #[YourBrand]
- [Trending hashtag]: [Monitor daily for relevance]
---
## Engagement Plan
**Reply SLAs:**
- Comments on your posts: Reply within 4 hours
- Mentions of your brand: Reply within 8 hours
- Direct questions: Reply within 24 hours
**Retweet Strategy:**
- Retweet 1–2 relevant posts per day
- Engage (like + comment) on 3–5 relevant posts daily
- Tag partners, customers, and industry voices when relevant
---
**Next Step:** Review calendar above. Approve content mix and scheduling. Export to social calendar tool (Buffer, Hootsuite, etc.) and begin scheduling.
Example
30-Day Social Calendar
Month: June 2026
Platforms: LinkedIn, Twitter
Key Themes: Ship Securely Not Slowly, Grow Without Rip-and-Replace, Transparent Pricing
Week 1: Launch Week
Monday (June 1)
- Platform: LinkedIn
- Pillar: Ship Securely, Not Slowly
- Hook: "Security reviews are killing your velocity. Here's how we cut them from 2 weeks to 2 days."
- Body: Most companies treat security as a gate after development. We flipped it: security is the foundation. Engineers ship with confidence. Security team reviews design, not implementation.
- CTA: "What's your security review time? Reply below."
- Engagement Target: 15+ comments, 30+ shares
Tuesday (June 2)
- Platform: Twitter
- Pillar: Ship Securely, Not Slowly
- Hook: "Your security team isn't slow. Your architecture is. Security-first design = 90% faster reviews."
- Body: [Link to blog post]
- CTA: Retweets welcome
- Engagement Target: 5% CTR, 2% retweet rate
Wednesday (June 3)
- Platform: LinkedIn
- Pillar: [Industry insight — data from Forrester on security bottlenecks]
- Hook: "72% of engineering teams cite security review delays as their #1 release bottleneck."
- Body: This isn't a security problem. It's an architecture problem. [Link to research]
- CTA: "What's holding back your releases?"
- Engagement Target: 10+ comments
Thursday (June 4)
- Platform: Twitter
- Pillar: Grow Without Rip-and-Replace
- Hook: "Started with [Competitor B], outgrew it at Series B, now $100M ARR. Cost us 6 months to migrate. There's got to be a better way."
- Body: There is. [Link to case study]
- CTA: Retweets welcome
Friday (June 5)
- Platform: LinkedIn
- Pillar: Transparent Pricing
- Hook: "Your pricing surprises customers when they hit $10M ARR. Ours doesn't."
- Body: We made a choice: linear pricing. Pay 10x for 10x usage. No surprise enterprise tax. No hidden tiers.
- CTA: "Do your customers know your final bill?"
- Engagement Target: 8+ comments
Analytics Targets (Weekly)
- Reach: 15K impressions (LinkedIn 10K, Twitter 5K)
- Engagement: 8% CTR on LinkedIn, 3% on Twitter
- Comments: 40+ high-quality comments (not spam)
- Follower Growth: +150 followers
- Traffic Driven: 200+ clicks to website from social
Copy Templates
LinkedIn Post Template
[Hook]: "Security reviews kill your velocity. Here's how."
[Story]: "Post-Series A, most engineering teams face the same problem: security becomes the bottleneck. You're shipping every two weeks, but getting sign-off takes twice as long."
[Proof]: "One customer cut their review time from 2 weeks to 2 days just by rearchitecting for security-first. Engineers code confident. Security team reviews design."
[CTA]: "What's your security review time? Tell me in the comments."
Twitter Template
[Hook + Insight]: "Security reviews are killing your velocity. Your architecture, not your team, is the bottleneck."
[Reply 1]: "Most teams add security after the fact. We embed it in the foundation. 90% faster reviews. Sounds impossible? We've done it with 50+ companies."
[Reply 2]: "Interested in how? Read the case study: [link]"
