← 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": "Create original images or video using available host creative tools and saved ReelGenie brand guidance and Favourites, then transfer generated originals directly into ReelGenie and carry out the requested delivery from chat.",
  "included_files": [
    {
      "relative_path": "references/carousel-qa.md",
      "size_in_bytes": 1924
    }
  ],
  "name": "create-content",
  "skill_md_contents": "---\nname: create-content\ndescription: Create original images or video using available host creative tools and saved ReelGenie brand guidance and Favourites, then transfer generated originals directly into ReelGenie and carry out the requested delivery from chat.\n---\nWhen the user asks to create a ReelGenie post, carry the request through finished media, private save and exact post review. Generating an image alone is not completion. If the user already requested the post, do not ask them to confirm saving it privately or to send a separate follow-up. Continue after the creative tool returns when the host permits it. If the host ends the turn or does not expose the generated file, report that specific limitation; never claim the post was saved without a successful save and readback.\n\nResolve the brand from the conversation and connected account; use the default workspace (or first authorized workspace) when the user has not named another brand. Never require a workspace-selection step. Keep internal workspace IDs in tool calls, not onboarding questions. When connected, read the resolved workspace profile and any chosen existing Favourite instructions/private reference images first. A newcomer without a Favourite can create from their own brief; do not require a saved reference or invent one. Preserve the brief and finished files through host-managed sign-in when saving. Preserve the chosen composition; develop an original topic, wording and imagery. Do not present source claims as verified facts or copy the creator's identity. Use relevant host creative skills/tools when available. ReelGenie never generates images or renders video. If the host cannot create finished assets, explain the missing capability and ask for finished media or an authorized creative service.\n\nFor performance-led requests, consult ../analyze-performance/SKILL.md; for externally researched topics/hooks, consult ../research-content/SKILL.md. Do not make either a prerequisite for a simple supplied brief. Keep source topic/hook, factual support and visual Favourite provenance separate. An explicit user-selected style and its valid campaign window supersede winner-based selection. Reuse existing Favourites without duplication; never invent winner provenance. Apply the latest explicit user direction before older guidance; do not carry expired campaign overrides into new posts.\n\nRead references/carousel-qa.md before generating a multi-slide post or promotional creative. Make the product's verified benefit part of the useful story where promotion is requested. Inspect all finished assets and their phone-size sequence, correct observed failures, and re-inspect before saving. Do not invent product screens, claims or statistics. No required popularity research for an original user brief.\n\nBefore retrying an uncertain save, reconcile `list_finished_posts`, `get_finished_post` and available request receipts against the expected brand/title/media. A timeout does not establish failure. Do not duplicate a possibly saved post or blindly repeat creation; if reconciliation cannot establish the outcome, report the specific uncertainty.\n\nInspect actual finished media before upload. Use `create_finished_image_post` for 1–10 ordered PNG/JPEG/WebP originals (8 MB each, 12 MB total). Choose the transfer from the actual available file representation before calling the save tool:\n\n- For a ChatGPT conversation attachment with a real host file reference, pass ordered references in `files`; the host supplies `download_url`, `file_id` and optional `mime_type`/`file_name`. ReelGenie downloads and preserves the originals automatically.\n- For Codex or ChatGPT Work generated files available only as filesystem paths (including `/workspace/`, `/mnt/data/` or local absolute paths), upload the exact files instead of passing base64: call `begin_finished_image_post` with `title`, optional `description` and `hashtags`, and one `{ mime_type, filename }` per file in carousel order; call `get_finished_image_upload_urls` with the returned `post_id`; PUT each file's bytes to its `upload_url` with the returned `content_type` header (for example `curl -X PUT -H \"Content-Type: <content_type>\" --data-binary @<file> \"<upload_url>\"`); then call `finalize_finished_image_post` with each file's SHA-256 in the same order. The upload URLs are secret, expire in an hour and are create-only: never print, log or store them. If finalize rejects one slide, request URLs again and upload only that slide. If the host cannot make an HTTPS PUT, fall back to `create_finished_image_post` with `images` (MIME and base64). A cloud Work filesystem path is still a filesystem path. Do not send such paths to `files` hoping they will become host references: that path timed out in the installed Work host. Do not re-encode, resize or regenerate the media. Do not paste base64, upload URLs or file contents into user-facing chat.\n\nWhen the post is text on coloured slides (tips, lists, a quote, a call to action) and the host has no image tool, or the user wants exact brand colours and type, use `create_slide_post` instead of making images: give a `title`, caption and hashtags, `slides` (1 to 10) and a `style`. ReelGenie renders the slides and saves the post for review.\n\nBefore writing a caption, read `list_caption_snippets` for the workspace's saved captions and hashtag sets and use them where they fit. When creating a post, pass `hook_description`: the first slide or opening frame a viewer sees, its on-screen text and its look, in one or two plain sentences. If the post is based on a saved Favourite, pass its `reference_template_id`. ReelGenie stores these with the post so results can be read against them later; leave a field out rather than guess. Use `add_post_note` to leave reviewers a short note (what changed, what to check); notes never change the post or its approval. `get_finished_post` returns notes people left for you: read and act on them.\n\nNever invent file IDs or URLs. Do not ask the user to download, choose files again, open a file picker, configure the browser extension or manually upload files already generated in the conversation. If this host cannot supply either transfer, state that specific integration limitation instead of presenting manual import as the normal workflow. Keep tokens out of tool output. For MP4 use `begin_finished_video_post`, `get_finished_video_upload_url`, a create-only PUT with the returned headers, then `finalize_finished_video_post`. A reserved upload is not a verified video. If host transfer is unavailable, use a precise manual console upload handoff.\n\nRead back the stored original manifest; compare SHA-256, byte sizes, order, title, caption and tags against the local files. Open `open_reelgenie_review` with the saved `post_id` and `account_group_id` when available, so the Post review tab shows that exact post. Use `get_reelgenie_review` as a fallback. Otherwise show the stored Post's console URL. Inspect the exact original preview, not a regenerated thumbnail. Save caption edits with the observed `expected_content_version` when supported; reload on conflict. Image replacements require the current image hash. Never approve or schedule merely because media was imported.\n\nUse embedded Post review as the single default review surface. After saving, call `open_reelgenie_review` once with the exact post and brand. Do not also open a web browser or console for routine preview/QA; inspect original media and the embedded review. Merely returning a console URL does not mean it should be opened. Open the web console only when the user chooses Go to ReelGenie, explicitly requests it, or the embedded host is genuinely unavailable and a fallback is needed; explain that fallback. An intentional console handoff for account connection or advanced settings remains separate.\n\nFor a request to save this style or source as a Favourite, follow ../manage-favourites/SKILL.md. For edits to an existing saved post, follow ../manage-posts/SKILL.md rather than creating another post.\n"
}

SHA-256 of public snapshot: 268b9194ccc899997f7164b20d45ef3583dd2d9f9f492ccf949009b1b063823e