Individual skill
recycle-top-posts
Find the user's best past social media posts in PostEverywhere and schedule fresh versions of them. Use when the user wants to reuse, recycle, reshare or "bring back" posts that did well, fill gaps in their schedule with proven content, or asks which old posts are worth posting again.
plugins/posteverywhere/codex-plugin/skills/recycle-top-posts/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,531
- 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
- writing 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 · 2,715 bytes
Read excerpt
# Recycle top posts
Find what worked before, write new versions of it, and space them out. A new version says the same idea in new words; it is never a copy.
## Steps
1. **Pick the period.** Default to the last 90 days. Call `get_analytics_summary` (`period: "custom"` with `from` and `to`) to see which platforms did best.
2. **Find the posts.** Call `list_posts_advanced` with `status: "published"`, `published_after` and `published_before`, `sort: "published_at"`, and `limit: 100`. Page with `offset` if there are more. Each destination carries its own numbers (views, likes, comments, shares) where the platform reports them.
3. **Rank them.** Rank by engagement on each platform, not across platforms: a good LinkedIn post and a good X post have different numbers. Use `get_post_results` for a closer look at the top few. Leave out posts that were about a date or offer that has passed.
4. **Show the shortlist.** List the top five to ten posts: platform, date, first line, and the numbers. Say "not available" when a platform didn't report a number. Ask the user which to recycle.
5. **Write new versions.** For each chosen post, write a fresh version: a new first line, a new angle or example, the same core idea and the same facts. Change the format when it helps (a tip list becomes a question, a quote becomes a short story). Follow the user's voice guide if there is one (see `brand-voice`).
6. **Space them out.** Leave at least a few weeks between a post and its new version on the same account. Call `list_posts_advanced` with `status: "scheduled"` to avoid clashes, or offer to use the posting queue (`get_queue`, then `use_queue: true`).
7. **Show the plan.** Present a table: date and time, accounts, the old first line and the new text. Ask the user to confirm.
8. **Create them.** After the user confirms, create them as drafts with `bulk_create_posts` (`draft: true` on each), or schedule them with each post's `scheduled_for` if the user said to. To reuse the original media, get its ids with `get_post`, check each one is still in the library with `get_media`, and pass them in `media_ids`.