Agent skill
social-batch
Turn one topic into a full content suite in one shot — Twitter/X thread + LinkedIn post + Instagram caption + Substack note + 5 standalone tweets. All pieces share the same core message but are adapted for each platform's style and format. Use when user wants to "batch content", "create a content suite", or produce multi-platform content from one idea.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/social-batch
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Social Content Batch
Purpose: Take one topic, idea, or piece of content and produce a complete multi-platform content suite in a single pass. Each piece shares the same core message but is natively adapted for its platform.
When to Activate
Use this skill when:
- User wants to batch content creation from one topic
- User mentions "content suite", "multi-platform", or "repurpose for social"
- User provides a topic and wants it adapted across platforms
- User wants to maximize output from one idea
Core Principle: Adapt, Don't Copy-Paste
Each platform has different:
- Audience intent (LinkedIn = professional growth, X = ideas + personality, Instagram = visual + lifestyle, Substack = depth + relationship)
- Format constraints (character limits, visual requirements, reading context)
- Engagement patterns (what gets shared, saved, commented on)
The same idea must be RE-EXPRESSED for each platform, not copied across them.
Output Components
1. Twitter/X Thread (8-10 tweets)
Format:
- Hook tweet with 🧵 emoji
- One idea per tweet, under 280 chars each
- CTA as final tweet
- Include character counts
Tone: Pithy, sharp, personality-driven. Compressed wisdom.
2. LinkedIn Post (300-500 words)
Format:
- Hook line (above the "...see more" fold)
- Story or observation
- 3-5 numbered insights
- CTA
Tone: Professional but human. Story-driven. No corporate speak.
3. Instagram Caption (Under 150 words)
Format:
- Hook line (before truncation)
- 2-3 sentences of value
- CTA
- 5-15 hashtags
Tone: Casual, personality-forward, visual-mindset.
4. Substack Note (3-7 sentences)
Format:
- Choose the best note type for this topic (see formulas below)
- Apply structural pattern
- Keep under 7 sentences
Note types: Single-punch wisdom, pattern observation, contrarian statement, problem→solution, list-based tactical, or direct advice.
5. Five Standalone Tweets (280 chars each)
Each tweet is a complete thought that can be posted independently throughout the week. Push the topic through different lenses:
- The bold claim — State the core idea with conviction
- The example — A specific instance that illustrates the point
- The question — Turn the idea into a thought-provoking question
- The contrarian angle — Challenge the conventional take on this topic
- The actionable tip — One specific thing the reader can do today
Include character counts for each.
Output Format
# Social Content Batch: [Topic]
**Core message:** [One sentence capturing the central idea]
**Source:** [Topic/content the user provided]
---
## 1. Twitter/X Thread
**Tweet 1** (XXX/280 chars)
[Hook tweet] 🧵
**Tweet 2** (XXX/280 chars)
[Body tweet]
[Continue for 8-10 tweets...]
**Tweet [N]** (XXX/280 chars)
[CTA tweet]
---
## 2. LinkedIn Post
**Word count:** [X] words
[Full LinkedIn post with hook, body, insights, and CTA]
---
## 3. Instagram Caption
**Word count:** [X] words
[Caption with hook, value, CTA]
.
.
.
[Hashtags]
---
## 4. Substack Note
**Type:** [Note type used]
[Full note]
---
## 5. Standalone Tweets
**Tweet A: The Bold Claim** (XXX/280 chars)
[Tweet]
**Tweet B: The Example** (XXX/280 chars)
[Tweet]
**Tweet C: The Question** (XXX/280 chars)
[Tweet]
**Tweet D: The Contrarian Angle** (XXX/280 chars)
[Tweet]
**Tweet E: The Actionable Tip** (XXX/280 chars)
[Tweet]
---
## Posting Schedule Suggestion
| Day | Platform | Content |
|-----|----------|---------|
| Monday | Twitter/X | Thread |
| Monday | LinkedIn | Post |
| Tuesday | Substack | Note |
| Wednesday | Twitter/X | Standalone tweet A |
| Thursday | Instagram | Caption + image |
| Friday | Twitter/X | Standalone tweet B |
| Weekend | Twitter/X | Standalone tweets C-E (spread out) |
Quality Checklist
- All pieces share the same core message
- Each piece feels native to its platform (not copy-pasted)
- Twitter thread: 8-10 tweets, char counts, hook + CTA
- LinkedIn post: 300-500 words, hook above fold, no corporate speak
- Instagram caption: Under 150 words, hashtags, visual-mindset
- Substack note: 3-7 sentences, right structural formula
- 5 standalone tweets: Different lenses, all under 280 chars
- Voice consistent across all platforms (adapted for tone, not changed)
- No hardcoded handles/links — pulled from context files
- Posting schedule provided
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?