← ReelGenieCONTENT HISTORY

Update to ReelGenie

Snapshot Nov 21, 2026 · 06:12 UTC · version 0.7.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save ReelGenie and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find and edit saved ReelGenie posts, change or cancel scheduled deliveries, diagnose failures, or delete and restore posts when requested.",
  "included_files": [],
  "name": "manage-posts",
  "skill_md_contents": "---\nname: manage-posts\ndescription: Find and edit saved ReelGenie posts, change or cancel scheduled deliveries, diagnose failures, or delete and restore posts when requested.\n---\nResolve the exact saved post from the conversation or `list_finished_posts`, paging when necessary; read `get_finished_post` before modifying it. Use the named brand or the default authorized workspace without a workspace picker. Use `search_mentions` for title discovery when appropriate, then read the resolved object; a bounded title match is not full post content. Follow ../setup/SKILL.md for connection and ../publish-content/SKILL.md for delivery authorization. Do not create a replacement post merely to edit an existing one.\n\nFor title/caption/hashtags/first-comment edits, use `update_post_social_metadata` with the observed `expected_content_version` and only requested fields. Verify the stored change and version. If an approval or pending send must be invalidated to permit editing, explain that consequence and use `return_post_to_review` only under the user's applicable instruction, with current version and confirmation/reason fields. Respect rejection of started or uncertain provider outcomes. Editing never authorizes re-publication; new delivery approval must cover the changed content.\n\nFor a single slide replacement, read the current manifest, inspect the requested original and use `replace_finished_image` with the exact slide index and current `expected_sha256`. Preserve the Post ID, other originals and original replacement bytes. Verify the resulting manifest/hash and inspect the saved slide. Follow ../create-content/SKILL.md for available creative tools and original-byte access. Do not re-encode other slides or fabricate a hash. Show the changed post once through `open_reelgenie_review`; do not also open the console.\n\nRead `list_scheduled_posts` to inspect calendar occupancy in the relevant workspace; show user-friendly local dates/times with the resolved timezone. Follow actual tool bounds and coverage, not assumptions about an empty calendar. A concrete instruction to move or cancel a named post authorizes that specified change, subject to host confirmation. Use `reschedule_post` for a new future instant, `update_scheduled_post_targets` for explicitly named connected destinations, and `cancel_scheduled_post` to stop a pending schedule. Read `list_connected_accounts` for exact account IDs and eligibility. For an approved unsent Post, use `update_post_publishing_options` to update timing/mode/exact targets together, with current version and applicable confirmation; it does not change originals or copy. For a READY_FOR_REVIEW Post, provide the selected options to `approve_post` under the delivery authorization in ../publish-content/SKILL.md. Do not replace a failed schedule with immediate publication or silently convert a publishing mode. Read back stored timing, targets and state with `get_finished_post` and `get_post_history`.\n\nFor failure recovery, use `diagnose_publish_failure` and stored per-destination history before proposing action. `retry_failed_scheduled_post` needs the exact Post, applicable confirmation and a future scheduled instant; preserve successful destinations and approved content. Unknown/processing/provider-accepted outcomes are not definite failure and must not be blindly retried. If a retry needs a new mode, account or time outside prior authorization, ask for that concrete change. Follow ../publish-content/SKILL.md for standing authorization and provider/inbox/public distinctions.\n\nFor another delivery of an already delivered post, use `create_another_delivery` only when the user requests the separate copy, setting `confirm_create_new_delivery` truthfully. It creates a review copy without sending and preserves the original. Verify and open that copy once; approve it only under applicable new delivery authorization.\n\nUse `soft_delete_post` only for an explicit deletion request identifying the Post, with confirmation/reason fields from the live schema. Explain that removing it from ReelGenie does not retract public social copies; pending-send cancellation must be confirmed by the stored state, not assumed after an uncertain response. For a requested restoration, read the deleted Post and use `restore_deleted_post` with its current `expected_deleted_at` and required confirmation/reason. Read back the result: restoration does not revive old delivery approval. Never broaden deletion, retry or restore to other posts.\n"
}

SHA-256 of public snapshot: f7fb34c96bb89be29cbcf4554b788ca5901092b4c0dca76910d91d21b8c81bc9