Generate X (Twitter) content based on community insights and trends. Use this skill when the user asks to "write a tweet", "create X content", "generate posts for X", "draft a thread", "write something for Twitter", "create a content calendar for X", "draft replies for X", "help me post on X", "write posts that match this community", "generate engagement content", "create a posting schedule", "write a reply to this tweet", or any request to create content for X/Twitter. Also trigger when the user wants to generate content that matches a specific community's tone, create a weekly posting plan, or draft engagement replies.
npx claudepluginhub msapps-mobile/claude-plugins --plugin x-content-intelligenceThis skill uses the workspace's default tool permissions.
Generate posts, threads, replies, and content calendars for X (Twitter) that match the tone, topics, and engagement patterns of a target community. Works best when combined with the x-insights skill for data-driven content creation.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Generate posts, threads, replies, and content calendars for X (Twitter) that match the tone, topics, and engagement patterns of a target community. Works best when combined with the x-insights skill for data-driven content creation.
Determine what the user needs:
Also determine:
If insights are available (from a previous x-insights run or user-provided context):
If no insights are available, ask the user:
Write posts that:
Structure threads that:
Draft replies that:
Build calendars that:
For every piece of generated content, self-check:
If any check fails, revise before presenting.
Present the generated content clearly:
For single posts: Show the post text, explain the reasoning behind the approach For threads: Show each tweet numbered, with a brief note on the thread's narrative arc For replies: Show the reply in context of what it's responding to For content calendars: Present as a table with columns for date, content type, topic, and draft text
Always ask if the user wants adjustments to tone, topic, length, or approach.
Rotate among these types for variety in calendars and batch generation:
| Type | Description | Example opener |
|---|---|---|
| Observation | Share a pattern or insight noticed | "Something I've noticed about..." |
| Question | Ask the community something genuine | "Curious how others handle..." |
| Discovery | Share something useful found | "Found something interesting..." |
| Before/After | Show a change or improvement | "Last month we... Now we..." |
| Hot take | Share a mildly contrarian opinion | "Unpopular opinion:..." |
| Appreciation | Highlight someone else's great work | "This thread by @... really clicked" |
| How-to | Share a practical tip or technique | "Quick tip that saved us hours:..." |
| Story | Tell a short, relatable narrative | "Last week I ran into..." |
If the user doesn't specify tone, offer these presets: