Individual skill
plan-content-calendar
Plan a week or month of social media posts with PostEverywhere. Use when the user asks for a content calendar, a posting plan, a batch of posts, "fill my queue", or a campaign across several days or platforms.
plugins/posteverywhere/codex-plugin/skills/plan-content-calendar/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,533
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- marketing Derived category
- writing Derived category
- productivity Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,926 bytes
Read excerpt
# Plan a content calendar
Turn a goal (a launch, a campaign, "keep my accounts active") into a set of drafts the user can review before anything is scheduled.
## Steps
1. **Understand the plan.** Ask for anything missing: the topic or goal, the date range, which accounts, and how often to post. Default to one post a day per platform when the user doesn't say.
2. **See what's already there.** Call `list_posts_advanced` with `status: "scheduled"` and the date range, so the new plan doesn't clash with posts already booked. Call `get_queue` to see the user's regular posting slots.
3. **Group it.** If the posts belong to one campaign, call `list_campaigns`, and create one with `create_campaign` if the user wants it grouped.
4. **Draft the posts.** Write each post for its platform (see the `schedule-social-posts` skill for the rules). Vary the angle across days; don't post the same text daily.
5. **Show the plan.** Present it as a table: date and time, accounts, and the first line of each post. Ask the user to confirm or change it.
6. **Create the drafts.** After the user confirms, send them with `bulk_create_posts` (up to 50 per call). Create them as drafts (`draft: true` on each) unless the user said to schedule them straight away. Use each post's own `scheduled_for`, or `use_queue: true` to let the queue pick the times.
7. **Report back.** List what was created and what, if anything, failed validation and why.