← PostEverywhereCONTENT HISTORY

Update to PostEverywhere

Snapshot Oct 29, 2026 · 19:13 UTC · version 1.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save PostEverywhere and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "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.",
  "included_files": [],
  "name": "recycle-top-posts",
  "skill_md_contents": "---\nname: recycle-top-posts\ndescription: 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.\n---\n\n# Recycle top posts\n\nFind 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.\n\n## Steps\n\n1. **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.\n2. **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.\n3. **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.\n4. **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.\n5. **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`).\n6. **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`).\n7. **Show the plan.** Present a table: date and time, accounts, the old first line and the new text. Ask the user to confirm.\n8. **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`.\n9. **Report back.** List each new post id, its accounts and its time.\n\n## Be honest\n\n- A small number of posts can't show what works. Say so when the sample is small.\n- Some platforms don't report every number. Don't rank a post low because its numbers are missing.\n"
}

SHA-256 of public snapshot: a57c8f2f3851d23f3ef89425cbee1bcfafa70a86f971f4f50531b95318febc11