← Your Social HubCONTENT HISTORY

Update to Your Social Hub

Snapshot Oct 24, 2026 · 13:33 UTC · version 1.1.4

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Your Social Hub and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Capture one user-described idea as a single entry in the Your Social Hub Ideas Hub. Use when the user asks to save a quick content idea, thought, hook, or note without a full drafting workflow.",
  "included_files": [],
  "name": "capture-idea",
  "skill_md_contents": "---\nname: capture-idea\ndescription: Capture one user-described idea as a single entry in the Your Social Hub Ideas Hub. Use when the user asks to save a quick content idea, thought, hook, or note without a full drafting workflow.\n---\n\n# Capture an idea\n\nCapture the user's current one-line idea as one Ideas Hub entry. Do not do voice research or create a batch.\n\n1. Resolve the calendar with `list_hubs` then `list_content_calendars`. Ask only when more than one calendar is plausible, and retain the user's choice for this conversation. Read the selected calendar's `formats` before creating the idea.\n2. Turn the idea into a `title` and `notes`. Include a `caption` only when the user supplied actual copy. Set `type` to the requested kind (`post`, `carousel`, `story`, `thread`, or `tiktok`); default to `post`. In particular, a carousel request requires `type: 'carousel'`, not `type: 'post'` with the word \"carousel\" in the title or notes.\n3. If the user names a format and the selected calendar contains a matching format, pass that existing format's id as `formatId`. A carousel request should use the calendar's `Carousel` format when present. Never invent a format id. If the format is unavailable, still set the correct `type` and tell the user that no calendar format was assigned.\n4. Call `create_idea` once. Do not send `fileOrder`. Set `publicationDate` only if the user supplied a date, formatted as full ISO-8601 UTC. Leave `socialAccountIds` unset unless the user named or selected accounts.\n5. Check the returned idea's `type`, `formatId`, `publicationDate`, and `socialAccountIds` against the request before reporting success. If the requested format was omitted and `update_idea` is available, set the existing calendar format id with `update_idea`, omitting `fileOrder`, and verify the returned idea. If `type` is wrong, do not claim that the requested kind was created; report the mismatch because `update_idea` cannot change `type`.\n6. When `render_social_preview` is available, call it with `entityType: 'idea'` and the newly created id so the user can inspect the idea in its platform frame.\n7. Report the created idea ID and title in one line. Say that the idea is planning-only until it is promoted to content for review.\n\nIf `create_idea` is absent, explain that `ideas:write` was not granted and ask the user to reconnect with that permission.\n"
}

SHA-256 of public snapshot: 76b11b3f45247abbeab9e0ff940a9334feb9e3ee02ae066306c61163ca755a9e