Rhythm
@starbucks posted 24 times in about six and a half weeks, roughly four a week, with bursts around Halloween and the holiday menu.
Threads Week Plan
Plan a realistic week of Threads posts from an account’s real rhythm and results.
v0.1.0
View example draft · How to useExample draft
A coffee roaster’s winter-menu week
10–16 November; at most one post a day; @starbucks as the reference.
The week
Five posts: two questions, one seasonal moment, one everyday line and one product post on Friday. Wednesday is kept for answering replies.
Why
Questions drew a median of 295 replies on the reference account; product posts were its weakest, so the menu is named once.
From a real run on 2026-11-08.
What you get
- Posts per week, busy days and usual hour
- What each kind of post earns
- A seven-day plan with a mix check
Good fit
- A launch or event week
- A small team that needs a plan it can keep
Not for
- Scheduling or posting
- Writing the posts; use threads-post-draft
How to use
An Agent that can read the complete Skill folder. Live research also needs a SandBase connection; supplied material can be used without a lookup.
Download and unpack the complete Skill folder, keep its references, and use it with a local Agent that supports Skills.
Ask your Agent
Use threads-week-plan for our winter-menu week starting Monday. Two people, at most one post a day. Use @starbucks as a guide.
Read the rhythm
Count posts per week and per day from the account’s recent posts.
See what earns what
Group posts by kind and compare likes, replies and reposts.
Lay out the week
Put real dates on their days and keep product posts to one or two.
FAQ
How do I use this Skill?
Download and unpack the whole Skill folder, including references, into your Agent’s supported Skill directory. You can also ask the Agent to read its SKILL.md and follow the instructions. Run it locally with your own material.
Why plan fewer posts than the reference account?
A big account has a social team. The plan is sized to what your team says it can keep.