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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Set a realistic publishing rhythm. The cadence should be ambitious enough to learn, but light enough to maintain quality and approvals.
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.
## Recommended Cadence
| Platform | Weekly Posts | Formats | Role | Notes |
| --- | --- | --- | --- | --- |
## Weekly Rhythm
| Day | Platform | Post Type | Time Window | Approval Cutoff |
| --- | --- | --- | --- | --- |
## Assumptions
- [assumption]
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."
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
The English summary is being prepared. Showing the original description.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
The English summary is being prepared. Showing the original description.
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
The English summary is being prepared. Showing the original description.
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
The English summary is being prepared. Showing the original description.
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
The English summary is being prepared. Showing the original description.