Pro X Workspace

A comprehensive skill for managing X (Twitter) marketing workflows — covering content creation, scheduling strategies, engagement analytics, thread composition, audience growth tactics, and brand voice consistency across X/Twitter campaigns.

When to Use This Skill

Choose Pro X Workspace when you need to:

• Create engaging X/Twitter content with proper formatting
• Plan content calendars and scheduling strategies
• Compose thread sequences for long-form content
• Analyze engagement metrics and optimize posting strategy
• Develop a consistent brand voice for X/Twitter

Consider alternatives when:

• You need multi-platform social media management (use a social media skill)
• You need X API integration for bots (use an API skill)
• You need paid advertising on X (use a social ads skill)

Quick Start

Copy
# Generate X/Twitter content
claude "Create 5 tweets for a SaaS developer tool launch. Product: CodeFlow — an AI-powered code review assistant. Include a mix of feature highlights, social proof, and engagement hooks."

Copy
# X Content: CodeFlow Launch

## Tweet 1 — Announcement
We just launched CodeFlow — an AI code review assistant
that catches bugs before your teammates do.

It reviews PRs in 30 seconds and explains issues
in plain English.

Try it free → [link]

## Tweet 2 — Feature Highlight
CodeFlow doesn't just find bugs.

It explains WHY the code is wrong and suggests
the exact fix.

No more cryptic linter messages. No more
"what does this error mean?" searches.

## Tweet 3 — Social Proof
"CodeFlow caught a race condition in our payment
service that 3 human reviewers missed."

— @engineer_name, Senior Dev at [Company]

We've already reviewed 50,000+ PRs in beta.

## Tweet 4 — Engagement Hook
What's the worst bug that made it past code review
at your company?

I'll go first: a typo in an env variable name that
sent production traffic to staging for 6 hours.

## Tweet 5 — Thread Starter
Why we built CodeFlow (a thread 🧵):

Last year, our team shipped a bug to production that
cost us $12,000 in downtime.

The fix was one line. The code review approved it
in 4 minutes without catching the issue.

We decided to fix code review itself → [1/5]

Core Concepts

Content Types for X

Content Type	Purpose	Best For
Single Tweet	Quick insight, announcement	News, tips, quotes
Thread	Long-form content, storytelling	Tutorials, case studies
Quote Tweet	Add commentary to existing content	Engagement, opinions
Poll	Audience engagement	Market research, fun
Reply/Engagement	Build relationships	Community building

Thread Composition

Copy
## Thread Structure (5-15 tweets)

### Tweet 1 — Hook
Grab attention. Promise value. Create curiosity.
"I increased my SaaS revenue by 340% in 6 months.
Here's the exact playbook (thread 🧵):"

### Tweets 2-N — Body
Each tweet delivers ONE point.
Start each with context from the previous tweet.
Use line breaks for readability.

### Final Tweet — CTA
Clear call-to-action:
- Follow for more
- Try the product
- Share the thread
- Reply with their experience

### Thread Tips
- Number tweets: [1/8], [2/8], etc.
- Each tweet should stand alone (shareable individually)
- Front-load value in tweets 2-3 (most drop-off happens here)
- Use a cliffhanger at tweet 3-4 to retain readers

Posting Strategy

Copy
## Optimal Posting Schedule

### Best Times (Engagement Data)
| Day         | Peak Times (UTC)     | Content Type       |
|------------|---------------------|--------------------|
| Mon-Fri    | 08:00-09:00         | Professional tips  |
| Mon-Fri    | 12:00-13:00         | Industry insights  |
| Mon-Fri    | 17:00-18:00         | Engagement posts   |
| Saturday   | 10:00-11:00         | Casual/fun content |
| Sunday     | 15:00-16:00         | Week-ahead threads |

### Posting Frequency
- Minimum: 1-2 tweets/day for visibility
- Optimal: 3-5 tweets/day (mix of original + engagement)
- Maximum: 8-10/day before diminishing returns
- Threads: 2-3 per week maximum

Configuration

Parameter	Description	Example
brand_voice	Tone and personality of the account	"professional yet witty"
content_focus	Primary topic area	"developer tools"
target_audience	Who you're trying to reach	"software engineers"
post_frequency	How often to post	"3-5 daily"
thread_length	Default thread length	"5-8 tweets"
include_hashtags	Use hashtags in posts	false (organic feel)

Best Practices

1. Write the hook tweet first, then build the thread around it — The first tweet determines whether anyone reads the rest. Spend 50% of your writing time on the hook. If the first tweet doesn't create curiosity or promise value, the thread dies there.

2. Use line breaks aggressively in tweets — Dense paragraphs are hard to read on mobile (where most X users are). Break after every sentence. White space is your friend. One idea per visual block.

3. Engage with replies for 30 minutes after posting — The algorithm rewards early engagement. When you post, stay on the platform and reply to every comment for the first 30 minutes. This signals to the algorithm that the content is generating conversation.

4. Avoid hashtag spam — One or two relevant hashtags are fine. Five hashtags looks like spam and reduces engagement. On X specifically, content without hashtags often performs better than content with them because it looks more organic.

5. Repurpose top-performing content — If a tweet gets 3x your average engagement, expand it into a thread. If a thread performs well, extract the best tweets as standalone posts. Recycle your best content every 3-4 months — your audience has grown and most didn't see it the first time.

Common Issues

Engagement drops after initial growth — Most accounts hit a plateau because they stop experimenting with content formats. If your engagement drops, change one variable: try threads instead of single tweets, try polls, try a different posting time. Test for two weeks before concluding.

Content sounds generic and interchangeable — If your tweets could come from any account in your niche, they lack voice. Inject personal experiences, specific numbers, contrarian opinions, and behind-the-scenes stories. "Use React" is generic. "We switched from React to HTMX and cut our bundle size by 90%" is distinctive.

Thread engagement drops off after tweet 3 — Front-load your best content in tweets 2-3 instead of saving it for the end. Most readers drop off by tweet 4. Put the payoff early and use the remaining tweets for supporting evidence, not the main point.