← Plugin catalog
Productivity

ReelGenie

ReelGenie v0.7.1

Review and schedule posts

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read
  • Write

Cost & access

The plugin does not sell products or process purchases. ReelGenie account subscription and billing are managed separately in the web console.

Declared limitations

  • An ambiguous publishing request must not approve an unspecified post or destination.
  • A changed post cannot reuse approval for an earlier content version. In the dedicated test account, edit a prepared post after its review or approval.
  • An uncertain provider outcome must not trigger a duplicate delivery. Use a reviewer fixture whose recorded state is processing or outcome unknown.

Onboarding example

Help me create my first social post with ReelGenie.

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

ReelGenie stores your finished images and video, supports exact preview and caption edits, and delivers to eligible connected accounts after your explicit approval. Creative tools depend on your host. TikTok inbox drafts require completion in TikTok.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 21, 2026. Last seen Nov 21, 2026.

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package17 files · 74.8 KBBrowse files →
Skill instructions
analyze-performance3.23 KB

View saved version →

---
name: analyze-performance
description: Analyze ReelGenie post reach and engagement, compare recent performers fairly, recover a winner's existing Favourite, and recommend measurable creative experiments.
---
Use when the user asks what performed well, requests a period review, or wants to create from a recent winner. Explicit user instructions take precedence. Read-only analysis does not approve posts, alter campaign settings or start an automation.

Use this plugin's bundled connection and resolve requested brands or the default automatically. Read `get_workspace_content_profile`. Use `get_recent_post_performance` for latest per-target counters, `get_latest_post_performance_all_groups` for requested cross-brand comparison, for accessible counters. The Performance panel uses paged `get_performance_review` for saved daily observations, but that tool is app-only: do not assume it can be invoked from chat when absent from the callable catalog. Open the panel through `open_reelgenie` if the user wants its chart. When daily observations are unavailable to the assistant, state that coverage gap and do not infer historical changes from current lifetime totals. Read `get_finished_post` and, when needed, `get_post_history` for content, publishing and recorded provenance. Observe returned limits/cursors; a three-post snapshot cannot support an exhaustive seven-day claim. If a requested period exceeds accessible coverage, state the coverage gap.

Read references/comparison-checklist.md before ranking or aggregating. Explain the time window, timezone, eligible/total post counts, platforms/accounts, metric freshness and exclusions. Distinguish creation date from public publication date; private drafts and provider-accepted inbox uploads are not measured public posts. Missing metrics remain unavailable, not zero. Compare within the same account/platform and reasonably comparable post ages; report small samples and unequal ages. Do not combine platform counters as though they measure identical audiences.

Inspect the strongest and weaker actual content to separate topic, hook, style and product treatment. State findings as observations, interpretations and testable hypotheses; simultaneous changes prevent attributing lift to one creative element. Report actionable next experiments and the evidence needed to judge them. Profile visits, clicks and installs require actual observed measurements/attribution; do not infer conversion from engagement.

When asked to create from a winner, state the ranking metric/basis, read the saved post and recover its ORIGINAL recorded Favourite with `get_reference_template` and `get_reference_image`. Do not create a new Favourite from the winner or guess provenance. An explicit user-selected style overrides winner-based selection; honor the active date window. If provenance is missing, use only an already authorized fallback and label it honestly, otherwise ask for the missing choice. With insufficient comparable measurements, report that no defensible winner is established; use an authorized selected style when available. Keep visual choice separate from the new topic's research. Continue the authorized request through ../research-content/SKILL.md as needed and ../create-content/SKILL.md without repeating resolved questions.

Referenced files: 1 — file references are metadata, not package contents.

create-content7.85 KB

View saved version →

---
name: create-content
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.
---
When 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.

Resolve 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.

For 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.

Read 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.

Before 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.

Inspect 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:

- 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.
- 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_finish

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

manage-favourites4 KB

View saved version →

---
name: manage-favourites
description: Save a post or visual reference as a ReelGenie Favourite, attach its reference images, or edit and remove an existing Favourite when requested.
---
Use 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.

Resolve 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.

Inspect 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.

Read `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.

Attach 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.

Verify 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.

For 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 del

Preview of the first 4,000 characters. Read full instructions →

manage-posts4.4 KB

View saved version →

---
name: manage-posts
description: Find and edit saved ReelGenie posts, change or cancel scheduled deliveries, diagnose failures, or delete and restore posts when requested.
---
Resolve 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.

For 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.

For 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.

Read `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`.

For 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.

For 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.

Use `soft_delete_post` only for an explicit deletion request identifying the Post, with confirmation/rea

Preview of the first 4,000 characters. Read full instructions →

publish-content6.77 KB

View saved version →

---
name: publish-content
description: Review finished ReelGenie media, confirm exact accounts and time, and read back schedule, delivery and raw performance.
---
Read the current stored Post and original media, then use `list_connected_accounts` for eligible destinations and `list_scheduled_posts` for current calendar occupancy in its workspace. Identify every destination by exact `social_account_id`, platform and display name. YouTube requires finished MP4. TikTok photos require compatible originals; inbox-draft delivery needs completion in TikTok. Do not claim public TikTok publication from draft delivery. Follow server/provider eligibility and existing publishing safeguards.

Show the exact saved caption/media, destinations and future time with timezone. A concrete conversational instruction to publish or schedule the shown post to identified accounts at a specified time is approval: use `approve_post` with its current version and exact targets to execute it without sending the user to a checkbox, panel, console or repeated confirmation. Ask only for missing or ambiguous destination, content or timing. Broad workflow intent and merely saving a draft do not approve a particular public delivery. Host-required confirmation still applies. Pass the observed `expected_content_version` when supported. If the execute scope is missing, use `request_publish_approval` as a proposal and console handoff; never elevate grants yourself.

To schedule, give one time for all accounts, a time per account (`publish_targets.<platform>.scheduled_publish_at`), or `schedule: "next_slot"` for each account's next free posting time; read `get_posting_slots` first and show each account's resulting time before approving. Before approving, call `check_post_delivery` with the same `publish_targets` and planned `scheduled_publish_at`. Approval is refused while any `block` check fails: show the user each failed check and fix it first. Pass warnings on in plain words, such as an account sign-in that will expire before the send or a shared daily limit already used up that day.

For TikTok Direct Post, read `get_tiktok_posting_options` for the account, then ask the user and never choose for them. Pass their answers in `publish_targets.tiktok.options`: who can view the post (`privacy_level`, from the allowed levels; there is no default), whether to allow comments and, for video, Duet and Stitch (each off unless they say yes), whether it promotes their own brand, a third party or both (`commercial_content`; branded content cannot be private), and whether to add TikTok's AI-generated label (`ai_generated`). Show TikTok's notice before confirming: "By posting, you agree to TikTok's Music Usage Confirmation", or "…Branded Content Policy and Music Usage Confirmation" for branded content. Instagram (`placement`, `collaborators`, `user_tags`, `alt_texts`, Reel `share_to_feed` and `cover_timestamp_ms`) and YouTube (`privacy_status`, `made_for_kids`) options go in the same target's `options` when the user asks for them.

If a TikTok or YouTube send fails with a daily limit (the shared TikTok app's account cap, the account's post cap, 5 waiting inbox drafts, a posting ban, the shared YouTube upload allowance or a channel's upload limit), do not retry it; tell the user what the message says and when to send again. A send whose result is unknown is never retried automatically: ask the user to check the account and record the outcome on ReelGenie's Delivery health page.

Read back the resulting stored manifest, metadata, exact targets, UTC schedule/timezone and scheduled state. A concrete user instruction to reschedule, change destinations, cancel or retry authorizes that specified operation; ask only when the intended operation is ambiguous or the host requires confirmation. Use the existing pipeline tools, diagnose stored failures before eligible retries, and preserve successful destinations. Do not silently publish now when scheduling fails.

Read status per destinatio

Preview of the first 4,000 characters. Read full instructions →

research-content2.92 KB

View saved version →

---
name: research-content
description: Find and verify relevant social post topics and hooks, inspect audience discussion, avoid recent repetition, and prepare a creative brief using ReelGenie brand guidance and an existing Favourite.
---
Use for requests to find popular posts, research hooks, discover the next topic, or create a post inspired by external examples. Explicit user instructions take precedence over these guidelines. A simple original brief does not require popularity research. Research never authorizes creation or delivery beyond the user's request.

Use this plugin's bundled connection for private data. Resolve named brands or the default workspace without a workspace picker; read `get_workspace_content_profile` and recent `list_finished_posts`, paging as needed. Apply the user's current audience, topic boundaries, product goals and dated experiments. Keep temporary campaign settings out of this skill. Separate the topic/hook source from the visual Favourite; use the existing selected Favourite through `get_reference_template` and `get_reference_image`, without duplicating it. If the user asks to reuse a winner's style, follow ../analyze-performance/SKILL.md to establish a defensible winner and recover its recorded Favourite.

For cross-platform research, search both TikTok and Instagram when available, using native platform search and host web discovery. For an explicitly single-platform request, honor that scope. Broaden from audience/stage synonyms to practical problems, desired outcomes, relevant products/ingredients/tools, everyday decisions and hook wording. Explore beyond familiar creators. Inspect primary posts directly; search snippets alone cannot verify their format, cover, metrics or discussion. Never infer permission to access another account or promise unavailable host browsing capabilities.

Read references/source-qualification.md before choosing a source. Record a concise brief: audience, concrete decision, useful payoff, primary source URL/date/creator, exact observed hook, visible metrics with observation date, relevant audience discussion, factual sources, distinct original points, verified product capability/action, chosen Favourite and provenance. Preserve ordinary short hook wording and edition framing when requested, with only supported factual corrections; write original substance and imagery rather than copying a creator's identity or full content.

If research is blocked, report attempts on each relevant platform, keyword families, strongest candidates and exact rejection/access reasons. An inaccessible platform or incomplete search is not evidence that no relevant sources exist. Continue useful available routes and unaffected brands without inventing popularity. Offer an original brief only when consistent with the user's requirements; do not silently relax a required verified-source gate. For creation, continue with ../create-content/SKILL.md rather than asking the user to repeat the brief.

Referenced files: 1 — file references are metadata, not package contents.

setup6.4 KB

View saved version →

---
name: setup
description: Start a first ReelGenie post, connect account access, or manage saved brand guidance and account settings when requested.
---
Keep the conversation as the primary interface: use the brief, generate with available host tools, transfer originals automatically, and execute concrete delivery instructions. Never require panel navigation or manual re-upload of conversation assets. Start with `open_reelgenie` only when the user wants the panel: its welcome and example workstation screenshot are available without sign-in. Keep initial conversation-led creation anonymous when no saved workspace context is needed. When the user wants to save or read private workspace content, call `connect_reelgenie` on this plugin's bundled connection. It requests host-managed sign-in with all supported content, performance and publishing scopes for the account. Each delivery still needs explicit post, destination and timing approval. Anonymous discovery intentionally omits private workspace/post tools. After linking, use the refreshed authenticated tool catalog; if the host does not refresh it, report that connection problem rather than using a separately configured server.

Welcome new users with one useful route: create a first post in the host conversation or review their own finished media. Ask for the topic or media if missing. Explain that ReelGenie saves, reviews and schedules finished content; creative tools depend on this host. Never imply a draft is already saved or an account is connected.

When a protected ReelGenie tool needs sign-in, let the host run the plugin's OAuth connection. The user signs in to ReelGenie, approves one account connection covering all supported plugin permissions, and returns to this conversation. The host exchanges the authorization code with PKCE and attaches its access token to MCP requests. Neither this skill nor the panel needs the token. Never ask for a pasted token or password, put credentials into tool arguments, or create admin grants. If host authentication fails, explain the actual connection failure and preserve the user's current brief/media; do not replace this plugin journey with manual bearer setup. The account connection covers all workspaces; keep per-post publishing approval separate from account consent.

Use this plugin's bundled ReelGenie MCP connection for this workflow. Do not silently fall back to separately configured ReelGenie developer/system MCP servers, whose credentials and permissions may differ. If the bundled connection is unavailable, report that installation/connection problem. After connection, check `reelgenie_health`, resolve the appropriate brand from their request and use the default workspace (or first authorized workspace) unless the user names another brand. Never add a workspace-selection step. Read the selected workspace profile and available Favourites. Reuse an existing selected Favourite without duplication; a newcomer with no Favourite can continue from their own brief and media. Keep brand guidance, reference instructions and the fresh topic separate.

Open `open_reelgenie` for the sidebar and `open_reelgenie_review` for the thread panel when available. Pass the exact saved `post_id` and `account_group_id` to `open_reelgenie_review` when reviewing a post from the conversation; an empty call opens the saved-post library. These are plugin UI surfaces, not account settings. Host capabilities vary; do not promise untested UI or transfer support. Keep the user's existing brief and media context across sign-in and verify any durable saved draft by readback.

Introduce connected social accounts when publishing or scheduling is requested. Social-account OAuth, membership, credentials and protected account changes belong in the ReelGenie console through `get_console_handoff`. Read back the result; an OAuth backend deployment or installed package alone does not prove the complete host workflow.

Route requests to the relevant bundled workflow: ../

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Release notes

0.7.1 adds direct file upload for finished images, rendered text slides, saved captions, posting slots, pre-send delivery checks, TikTok Direct Post choices and reviewer notes. Daily-limit failures are explained, not retried. No private account settings or delivery authorization bundled.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
ReelGenie
Getting started skill
./skills/setup/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Read
  • Write

Package observed Nov 21, 2026.

Technical details
First seen
Nov 21, 2026 · 06:00 UTC
Last seen
Nov 21, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6af1945ec73481919c1620df704519b4

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.