Cadence planner
Choose a practical social media posting cadence by channel, campaign period, audience, available assets, and review capacity. Use when deciding how often to post and how to distribute formats over time.From its SKILL.md
npx -y skills add agentreacher/skills --skill cadence-plannerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, 390 tokens by cl100k_base, as published. Nobody here has run it
Cadence Planner
Set a realistic publishing rhythm. The cadence should be ambitious enough to learn, but light enough to maintain quality and approvals.
Inputs
- channels
- period length
- campaign goal
- team capacity
- asset availability
- approval process
- minimum and maximum posting frequency
- time zone or audience geography
Workflow
-
Estimate capacity: writing, editing, creative assets, approvals, and publishing windows.
-
Choose a channel mix: primary channels get original posts; secondary channels get adapted or lighter posts.
-
Assign weekly frequency: split by platform, format, and pillar.
-
Add time slots: use sensible daypart assumptions and mark them as adjustable if no data is available.
-
Add constraints: rest days, approval cutoff, asset deadlines, and launch-day exceptions.
Taste Rules
- Fewer high-quality posts beat a brittle high-volume plan.
- Cadence should match the buyer journey and platform norms.
- Do not recommend video frequency unless there is production capacity.
- Treat launches differently from evergreen periods.
- State assumptions instead of pretending to know best posting times.
Output Format
## Recommended Cadence
| Platform | Weekly Posts | Formats | Role | Notes |
| --- | --- | --- | --- | --- |
## Weekly Rhythm
| Day | Platform | Post Type | Time Window | Approval Cutoff |
| --- | --- | --- | --- | --- |
## Assumptions
- [assumption]
AgentReacher Notes
Use this before AgentReacher scheduling to decide how many posts the agent should create and where the calendar needs human review.
Example usage in AgentReacher: "Plan a realistic 6-week cadence for X, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Threads, and Bluesky with two hours of review time per week."
What ships with it: 1 file
244 B alongside SKILL.md
agents/
- openai.yaml244 B