- Home
- Skills
- Marketing & SEO
- Content Repurposer — 1 Source to 7 Days of Posts
Works with the AI Agents you already use
Content Repurposer — 1 Source to 7 Days of Posts
Turn one article or video into a 7-day social media campaign with platform-native posts and scripts.
Free
Content Repurposer — 1 Source to 7 Days of Posts
Example session with this skill installed
Repurpose this article into a content calendar: https://example.com/blog/scaling-postgresql-databases. Target developers and use a technical but helpful voice.
- Read your context and instructions
- Compiled the content repurposer
I have processed the article on scaling PostgreSQL. I've extracted the core thesis regarding horizontal vs. vertical scaling and prepared a 7-day distribution pack.
Repurpose pack — Scaling PostgreSQL Databases
Core thesis: Scaling PostgreSQL effectively requires a transition from vertical hardware upgrades to horizontal strategies like connection pooling and read replicas before considering sharding.
Calendar
| Day | Platform | Asset | Time Window |
|---|---|---|---|
| 1 | Post 1: Vertical vs Horizontal | 09:00 - 11:00 | |
| 2 | X / Twitter | Thread: 5 Connection Pooling Tips | 12:00 - 14:00 |
| 3 | Post: How we handled 10k concurrents | 15:00 - 17:00 | |
| 4 | Short video | Script 1: The Indexing Trap | 10:00 - 12:00 |
| 5 | X / Twitter | Single Tweet: The Sharding Myth | 11:00 - 13:00 |
| 6 | Carousel: 7 Steps to Read Replicas | 18:00 - 20:00 | |
| 7 | Newsletter | Full Issue: Scaling Roadmap | 08:00 - 10:00 |
Post 1
Stop throwing RAM at your PostgreSQL problems.
Vertical scaling works until it doesn't. When your instance hits the ceiling, you need a strategy that doesn't involve a bigger bill from AWS.
We found that moving to a primary-replica model reduced our main instance load by 40% in 48 hours.
What is your first move when CPU spikes?
#postgresql #database #backend
X
Thread
1/ Scaling PostgreSQL is a journey, not a single configuration change. If you're hitting performance bottlenecks, here is the roadmap we used to scale to 10k+ concurrent users. 🧵
2/ First: Connection Pooling. Postgres creates a process per connection. Use PgBouncer to manage this overhead. It's the cheapest win you'll find.
3/ Second: Read Replicas. Move your heavy SELECT queries away from the primary. Most apps are read-heavy; this buys you massive headroom.
4/ Third: Partial Indexing. Don't index the whole table if you only query active rows. Smaller indexes = faster writes.
5/ Summary: Start with pooling, move to replicas, and only shard if you've exhausted everything else.
Next steps
- Review the Reddit post draft for r/PostgreSQL rules.
- Record the "Indexing Trap" short video using the provided script beats.
- Copy the LinkedIn post and add the article link in the first comment.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop wasting hours manually rewriting your articles for different social feeds. This skill takes a single source—a blog post, YouTube transcript, PDF, or URL—and extracts the core insights to build a complete multi-platform campaign. It produces platform-native drafts for LinkedIn, X, Reddit, Instagram, and newsletters without the repetitive "as mentioned in my blog" filler.
What it does
- Source extraction identifies the core thesis, standalone tips, stories, and contrarian points from any input.
- Platform adaptation drafts LinkedIn posts with specific hook constraints and X threads following a promise-then-summary structure.
- Community-specific writing builds value-first Reddit posts and identifies relevant subreddits without a marketing tone.
- Visual & video scripting generates short-form video scripts (TikTok/Reels) and slide-by-slide Instagram carousel plans.
- Campaign scheduling organizes all generated assets into a logical 7-day posting calendar with suggested time windows.
How it works
- Provide a source URL, file, or raw text and specify any brand voice preferences or target audiences.
- The skill extracts a raw material list including key insights, examples, and quotable lines.
- It generates platform-specific drafts according to strict character limits and formatting rules for each social network.
- You receive a structured "Repurpose Pack" containing the core thesis, the 7-day calendar, and all drafted assets for review.
Frameworks & tools
This skill works with any text-based input, PDF files, or public URLs. It outputs GitHub-flavored Markdown compatible with any code editor or project management tool.
Why this beats prompting it yourself
Generic prompts often result in copy-pasted text that ignores platform-specific nuances like LinkedIn's "link in comments" rule or X's character constraints. This skill enforces specific formatting logic for each network, ensuring hooks are the correct length and tone is adjusted for high-friction environments like Reddit.
Use cases
- Convert a long-form technical guide into a high-signal 7-tweet X thread.
- Turn a podcast transcript into a series of short-form video scripts for TikTok.
- Draft a value-first Reddit post from a product announcement to build community trust.
- Generate a week of LinkedIn content from a single company whitepaper.
Known limitations
This skill does not auto-post to social media accounts. It provides drafts for manual review and does not generate actual image or video files, only scripts and text-based slide descriptions.
Does not auto-post to socials. Does not generate image or video files (scripts only). Limited to source material provided; will not invent external stats.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
This skill has been used 2 times.
Trust & safety
Security scan
Security scan passed 5 days ago
- Free with an Agensi account