Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Take one piece of long-form content and atomize it into 10-20 platform-specific posts across 8 platforms (Twitter/X, LinkedIn, Instagram, Reddit, TikTok, YouTube, Threads, Bluesky). Turns blog posts, podcasts, videos, and newsletters into native social content for each platform. Use this skill whenever someone has existing content they want to distribute — even if they don't say 'atomize' explicitly. Triggers include: 'repurpose this', 'turn this into posts', 'social content from my blog', 'I wrote an article and want to promote it', 'cross-post this', 'content distribution', 'break this down for social', 'I have a podcast episode', 'turn this video into clips', 'make social posts from this', 'content calendar from this article', or any request to get more mileage from existing content.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You take one piece of long-form content and extract 10-20 standalone social posts, each native to its target platform. Not lazy copy-paste with different character counts — genuine reformatting that makes each post feel like it was written platform-first.
brand/voice-profile.md — maintain consistent voice across platformsbrand/audience.md — know which platforms matter and how the audience behaves on eachreferences/platform-specs.md for the quick reference table, then load individual platform files from references/platforms/ as needed (linkedin.md, twitter.md, instagram.md, tiktok.md, youtube.md, threads.md, bluesky.md, reddit.md)marketing/content/ for recent articlesIf brand files don't exist, the skill still works:
Brand files shape how content gets adapted per platform:
Read the source content and extract:
Tag each extraction with its type. This is your raw material inventory.
Each extraction type maps naturally to specific platforms and formats:
| Extraction Type | Twitter/X | TikTok | YouTube | Threads | Bluesky | |||
|---|---|---|---|---|---|---|---|---|
| Key insight | Single tweet | Text post | Carousel slide | Comment/post | Hot take (15s) | Short (30s) | Single post | Single post |
| Quotable line | Quote tweet | Text post with context | Quote graphic caption | — | Green screen | — | Quote-post | Thoughtful take |
| Stats/data | Data tweet | Data post with analysis | Infographic caption | Data post | Data reveal (20s) | Short (30s) | Mini-thread | Link post |
| Story | Thread opener | Story post | Story caption | Long-form post | Story format (30-60s) | Long-form (8-12m) | Conversational post | Experience report |
| Contrarian take | Hot take tweet | Debate post | — | Discussion post | Controversy spark (15s) | Short (15s) | Friendly disagreement | Informed take |
| Step-by-step | Thread | Carousel/document | Carousel | How-to post | Tutorial (30-60s) | Long-form (8-12m) | Mini-thread | Thread |
| List | Thread or single | Listicle post | Carousel | List post | Listicle (20s) | Short (45s) | Single post | Single post |
Load the specific platform file from references/platforms/ for full playbooks, algorithm signals, templates, and hook formulas.
Character limit: 280 per tweet, threads unlimited
Single Tweet Formula:
[Hook — pattern interrupt or bold claim]
[1-2 sentences of value or proof]
[CTA or takeaway]
Thread Formula:
Tweet 1: Hook — the big promise or contrarian take (this sells the thread)
Tweet 2-N: One idea per tweet, each must standalone
Final tweet: Summary + CTA + "Follow for more [topic]"
Rules:
Hook patterns that work:
Character limit: 3,000 per post
Post Formula:
[Hook line — stops the scroll]
[Line break]
[Story or context — 3-5 short paragraphs]
[Key insight or lesson]
[Call to engage: question, agree/disagree, share your experience]
[3-5 hashtags at the bottom]
Rules:
Hook patterns:
Character limit: 2,200 per caption
Caption Formula:
[Hook line — first 125 characters show in feed]
[Value content — tips, story, insight]
[CTA — save this, share with someone, comment your take]
.
.
.
[Hashtags — 5-15 relevant ones]
Carousel Strategy:
Rules:
Rules are different here. Reddit hates marketing.
Post Formula:
Title: [Specific, descriptive, no clickbait]
Body:
[Context — who you are, why you're sharing]
[The actual value — detailed, generous, no gatekeeping]
[Results or proof if applicable]
[Question to invite discussion]
[NO self-promotion links in the body]
Rules:
| Goal | CTA |
|---|---|
| Engagement | "What's your take?" / "Agree or disagree?" |
| Follows | "Follow for daily [topic] tips" |
| Saves | "Save this for when you need it" |
| Shares | "Tag someone who needs to hear this" |
| Traffic | "Link in bio" / "Link in comments" |
| Email capture | "I wrote a deeper guide — link in bio" |
For each source piece, output a directory:
marketing/social/{source-slug}/
├── twitter-threads.md # 2-3 threads with hook tweets
├── twitter-singles.md # 5-8 standalone tweets
├── linkedin-posts.md # 3-5 LinkedIn posts
├── instagram-captions.md # 2-3 captions with carousel briefs
├── reddit-posts.md # 1-2 Reddit posts with subreddit targets
├── tiktok-scripts.md # 1-2 short video scripts (15-60s)
├── youtube-shorts.md # 1-2 YouTube Shorts scripts
├── threads-posts.md # 2-3 Threads posts or mini-threads
└── bluesky-posts.md # 2-3 Bluesky posts
Only generate files for platforms the user wants. If no preference stated, generate for all 8 platforms. If source content is short (under 500 words), reduce to 6-10 posts across fewer platforms rather than stretching thin.
Each post includes:
---
platform: twitter | linkedin | instagram | reddit
type: thread | single | post | carousel | story
source: "original-content-slug"
hook: "first line preview"
character_count: 247
hashtags: ["tag1", "tag2"]
suggested_time: "Tuesday 9am ET"
status: draft
---
| Platform | Best Times (ET) | Frequency |
|---|---|---|
| Twitter/X | 8-10am, 12-1pm, 5-6pm | 1-3x daily |
| 8-10am Tue-Thu | 3-5x weekly | |
| 11am-1pm, 7-9pm | 4-7x weekly | |
| 6-9am, varies by sub | 2-3x weekly | |
| TikTok | 7-9pm Tue/Thu | 3-5x weekly |
| YouTube Shorts | 9-11am Sat | 2-3x weekly |
| Threads | 9-11am daily | 3-5x weekly |
| Bluesky | 10am-12pm weekdays | 3-5x weekly |
Space out atomized content over 1-2 weeks. Don't dump everything the same day.
| Anti-Pattern | Why It Fails | Instead |
|---|---|---|
| Copy-paste the same text across platforms | Platform algorithms detect duplicate content and suppress it. Users who follow you on multiple platforms see identical posts and feel spammed. Each platform has different character limits, norms, and audience expectations. | Rewrite natively for each platform's format and voice |
| Reuse the same hook pattern in a batch | When 5 posts in a row start with "Here's what I learned:", the algorithm treats it as low-variety content and your audience scrolls past. Batch monotony is the #1 tell of AI-generated content. | Vary hook formulas — alternate numbers, stories, contrarian, question |
| Atomize everything regardless of source length | A 300-word email stretched to 15 posts produces hollow filler. Each post needs a standalone insight — if the source doesn't have enough, the posts won't have enough. | Under 500 words → 6-10 posts max. Under 200 words → don't atomize |
| Post all atomized content the same day | Followers see 8 posts from you in one feed scroll and either mute or unfollow. Algorithms also penalize velocity spikes from a single account. | Space over 1-2 weeks with variety in timing |
| Ignore platform culture (marketing speak on Reddit, hashtag spam on Twitter) | Reddit moderators remove overt marketing. Twitter's algorithm deprioritizes hashtag-heavy tweets. Each platform's community has unwritten rules about tone and format. | Read the platform rules in this skill and adapt |
| Over-hashtag | Twitter and LinkedIn algorithms now treat excessive hashtags as spam signals. On Reddit, hashtags don't exist. Only Instagram still rewards them, and even there the trend is toward fewer. | Twitter: 0-1. LinkedIn: 3-5 at bottom. Instagram: 5-15. Reddit: 0 |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Add a new sound effect to @remotion/sfx
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。