threads-content-planner
Skill52 starsChanged 4 months agoMITView on GitHub
Generate a weekly Threads (Meta) content plan from a theme, audience, and content pillars. Produces per-day recommendations (single post vs thread, Threads hook formula, angle, posting time, primary goal), a single-to-thread mix, daily reply and quote-post targets, and a goal-mix balance check across replies, reposts, likes, and quotes. Use when the user wants to plan a week of Threads content instead of ad-hoc posting. Not for drafting one post or thread (use threads-post-writer).
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- threads-marketingSkill
- threads-audience-insightsSkill
- threads-hook-extractorSkill
- threads-humanizerSkill
- threads-post-writerSkill
- threads-profile-optimizerSkill
- threads-reply-drafterSkill
- threads-repurposerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Before a launch week (the plan aligns a product pillar)
- Distinctive: line 69
Every formula earns a primary signal.
- Distinctive: line 92
One formula per slot, varied across the week: Do not stack three T7 threads.
- Distinctive: line 110
Add daily reply/quote-post targets with a suggested template.
- Distinctive: line 111
Run the weekly balance check and the goal-mix check.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Threads Content Planner
Produce a weekly Threads plan built around a pillar discipline and the warm, conversation-first cadence Threads rewards. Threads moves fast like X and rewards posting multiple times a day, so the plan mixes single posts, threads, and reply/quote-post targets.
When to use
- User asks "plan my week on Threads" or "what should I post this week"
- User wants to escape ad-hoc posting and establish a rhythm
- Before a launch week (the plan aligns a product pillar)
Input
- Theme (optional): e.g. "shipping our AI agent in public"
- Audience description: e.g. "indie builders, AI engineers, early founders"
- Pillar mix (optional): defaults to 40% Build-in-Public / 30% Insight / 20% Engagement / 10% Promotion
- Posting cadence (optional): defaults to 2 posts/day on weekdays
- Voice samples (optional): past posts for voice calibration
Output
A markdown plan with:
7-day calendar
| Day | Slot | Type | Pillar | Formula | 1-line angle | Goal | Time |
| Mon | AM | single | Insight | T1 Warm Contrarian | "speed is a revenue line item" | reposts | 9:30 AM |
| Mon | PM | reply block | Engagement | R-templates | 5 builder conversations | replies | 12:30 PM |
| Tue | AM | thread | Build-in-Public | T10 How-I Teardown | "how we cut deploy 40m to 6m" | reposts | 8:30 AM |
| Tue | PM | single | Insight | T2 Data-Point | "1.3s page = 2.4x conversion" | reposts | 12:30 PM |
| Wed | AM | thread | Insight | T7 Listicle-Thread | "9 landing-page mistakes" | reposts | 9:00 AM |
| Thu | AM | single | Build-in-Public | T3 Confession | "the metric we hid for a month" | replies | 8:30 AM |
| Fri | AM | single | Engagement | T6 Relatable | "friday deploy energy" | likes | 9:00 AM |
(The skill fills real angles from the theme. Weekends are optional and skew to story threads or relatable singles, which travel well on Threads off-hours.)
Daily reply and quote-post targets
For each day:
- 5-10 accounts to engage (names or archetypes: "peer builders at 2-20k", "AI founders shipping in public", "the creators whose threads you repost")
- Template to apply (R1 answer, R2 concede-sharpen, R3 extend, R5 value-add quote)
- Target: 5-10 substantive replies per day. On Threads, replies on other people's posts drive more profile visits and follows than your own posts early on, and replies are the heaviest ranking signal.
Weekly balance check
- Single-to-thread mix roughly 65/35 (singles for cadence, threads for depth)
- At least 1 build-in-public post (real number from your work)
- At least 1 repost-bait post (list, framework, or how-to)
- At least 1 engagement/reply-heavy day
- No pillar over 60% of the week's posts
- No formula repeated more than twice in the week
- Goal mix spread (see below): not every post chases the same signal
Goal mix (balance the week)
Every formula earns a primary signal. A week that is all repost-bait or all reply-bait reads as engineered. Spread the goals:
| Goal | Formulas | Weekly target |
| Replies | T3, T9, T1 | at least 2 (Threads is conversation-first) |
| Reposts | T2, T5, T7, T10 | at least 2 (reposts are the save analog) |
| Likes | T6, T8 | at least 1 |
| Quotes | T4, T8 | at least 1 |
Rules
- 2-3 posts/day is fine on Threads. It moves fast and rewards conversation, but quality still gates: do not pad to hit a count.
- Single-to-thread mix ~65/35. Singles keep you present daily; threads earn the reposts and follows.
- Replies are a content type, not an afterthought. Block reply time daily; early growth on Threads comes more from replies than from posts, and replies are the heaviest signal.
- Weekday mornings (8-11 AM local) and a 12-1 PM lunch bump are the primary windows; 7-10 PM works for relatable and story content.
- Promotion pillar max 1-2 posts/week. Overuse kills trust fast on a community-first platform.
- One formula per slot, varied across the week. Do not stack three T7 threads.
- Keep the tone warm. Threads punishes a transplanted combative X voice.
Formula -> pillar mapping
| Pillar | Preferred formulas |
| Build-in-Public | T3 Confession, T10 How-I Teardown, T8 Story Thread |
| Insight | T1 Contrarian, T2 Data-Point, T7 Listicle-Thread, T9 Curiosity-Gap |
| Engagement | T6 Relatable, T4 Quote-Post, reply templates |
| Promotion | T10 (results that imply the product), T2 (your own data) |
Steps
- Gather inputs. Ask for theme, audience, pillar preferences if not provided.
- Validate the pillar mix sums to 100%; warn if any pillar is over 60%.
- For each day and slot, pick: type (single/thread/reply block), pillar, formula (do not over-repeat), angle, posting time (audience timezone), goal.
- Add daily reply/quote-post targets with a suggested template.
- Run the weekly balance check and the goal-mix check; flag anything missing.
- Return as markdown, plus optional JSON for import.
Example
See references/example-week.md for a filled-in 7-day plan.
Files
SKILL.md- this filereferences/example-week.md- worked 7-day planreferences/pillars-framework.md- the Threads pillar discipline explained
Related skills
threads-post-writer- draft each single post or thread from the planthreads-reply-drafter- execute the daily reply targetsthreads-hook-extractor- study competitors' posts while planning
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.