← 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": "Start a first ReelGenie post, connect account access, or manage saved brand guidance and account settings when requested.",
  "included_files": [
    {
      "relative_path": "references/account-management.md",
      "size_in_bytes": 2313
    }
  ],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Start a first ReelGenie post, connect account access, or manage saved brand guidance and account settings when requested.\n---\nKeep 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.\n\nWelcome 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.\n\nWhen 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.\n\nUse 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.\n\nOpen `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.\n\nIntroduce 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.\n\nRoute requests to the relevant bundled workflow: ../research-content/SKILL.md for topic/hook discovery, ../analyze-performance/SKILL.md for results and winner selection, ../create-content/SKILL.md for generation/private review, ../publish-content/SKILL.md for authorized delivery, ../manage-favourites/SKILL.md for saving or managing reusable references, and ../manage-posts/SKILL.md for existing-post edits, calendar changes and recovery. Read references/account-management.md only for requested saved brand guidance or account/workspace management. Users can describe their goal naturally; do not require skill names or configuration steps. Apply explicit user instructions over skill guidelines, preserve established context and ask only for essential missing information.\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 first-post onboarding, use a short natural conversation. Offer adapting an existing post into original content in the user's style, finding relevant trending topics, choosing a suitable topic, or the user's own idea. Ask one essential question at a time, using host-supported suggested replies when available; do not claim to render buttons or an input if the host lacks that capability. A brief sent from the welcome chooser already selects the route: continue it without asking the user to choose again. For adaptation, ask for the source only if missing; for trends, verify evidence through research-content rather than inventing popularity. Never expose a long technical instruction block as the user's starting request.\n\nAccount limits: preserve the saved post and explain the actual entitlement; ordinary user-facing quota messages say tomorrow without UTC jargon. Offer another date or keeping the post saved; do not automatically retry delivery. `get_console_handoff` with `operation: billing` opens informational account limits only. Do not advertise plans, suggest upgrades, initiate subscriptions or link checkout from the plugin. Refresh existing entitlement with `list_reelgenie_workspaces` when requested.\n"
}

SHA-256 of public snapshot: 08cd7ddfa70c0cfe9c2a8e9a38d7bb2de24c87ce17c8c6ae0a4acae58c51b586