← 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": "Save a post or visual reference as a ReelGenie Favourite, attach its reference images, or edit and remove an existing Favourite when requested.",
  "included_files": [],
  "name": "manage-favourites",
  "skill_md_contents": "---\nname: manage-favourites\ndescription: Save a post or visual reference as a ReelGenie Favourite, attach its reference images, or edit and remove an existing Favourite when requested.\n---\nUse the bundled connection; follow ../setup/SKILL.md only if connection is needed. Favourites are shared across the team's workspaces, not duplicated for each brand. A request to save a Favourite authorizes that private save, not creation or publication of a new social post. Reuse existing Favourites for ordinary content generation; do not save every researched or generated post automatically.\n\nResolve the actual source from the user's link, selected post or conversation. `create_reference_template` requires a real HTTPS `reference_url`, a name and reusable instructions. For an already saved ReelGenie post, verify its ID with `get_finished_post` and use the canonical HTTPS console route `https://reelgenie.app/app/posts/<observed-post-id>` as the source; do not open that page merely to save the Favourite. Do not fabricate a source URL or silently create a separate post just to obtain one. If an image-only reference has no usable source URL, explain this current tool constraint and ask only for the missing source. Do not ask the user to select a workspace, download or re-upload available images.\n\nInspect the source and available original images. Describe reusable hook structure, slide sequence, typography, composition, visual style and caption approach in `instructions` (maximum 4,000 characters), keeping them brand- and workspace-neutral. Keep the user's brand profile and next topic separate. Preserve a supplied name; otherwise choose a useful short name. Include `post_description` or `stats` only when actually observed; omit unavailable counters rather than inventing or treating them as zero.\n\nRead `list_reference_templates` for likely existing sources; this list is bounded, so a missing entry does not prove uniqueness. Call `create_reference_template` for the requested new source. The server enforces source identity across tracking URL variants and may return already-exists with the existing `template_id`; read that Favourite with `get_reference_template` and report that it is already saved. Do not overwrite its instructions or attach duplicate images unless the user requested that change. A timeout is uncertain: reconcile the source before repeating creation.\n\nAttach accessible original images using `add_reference_image`: PNG/JPEG/WebP, at most 8 MB each and 20 images per Favourite, in intended display order. This tool accepts MIME and base64 bytes, not the `files` download-reference form used for finished posts. Read the exact available conversation/generated files using host file-capable tools; never put base64 into chat or invent file references. If the host cannot retrieve the bytes, distinguish saved instructions from missing reference images. When an image add times out, read the saved manifest and compare hash/size/order before retrying; do not blindly duplicate the image.\n\nVerify with `get_reference_template`: source, name, instructions and ordered image count/checksums. Use `get_reference_image` to inspect saved reference pixels when needed. Only claim the parts actually saved. Let the user continue in chat or open the Favourites panel through `open_reelgenie` when requested; no additional web view by default.\n\nFor edits, read the current Favourite and use `update_reference_template` with its `expected_updated_at`, preserving unchanged required name/source/instructions. Reload on conflict; do not overwrite a concurrent edit. For a requested image removal, identify the exact image and use `remove_reference_image` with the current `expected_updated_at` and truthful `human_confirmation` required by the live schema. `delete_reference_template` removes a Favourite and its private images: require an explicit request identifying the Favourite, use the current timestamp and confirmation fields, and verify removal. Clarify an ambiguous deletion; respect any host confirmation. Removal is separate from deleting or retracting social posts.\n"
}

SHA-256 of public snapshot: 14de2423267fe0d1f78ce3d5112d68878473784b497d29de7eabfbf312a5a890