← Magister MarketingCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Magister Marketing
Snapshot Sep 30, 2026 · 23:07 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "magister-social-publishing",
"description": "Draft, schedule, and publish social posts through Magister, and read post and follower analytics. Use when the user wants to write a social post in their brand voice, schedule content, publish a draft, see how posts performed, or find the best time to post.",
"included_files": [],
"skill_md_contents": "---\nname: magister-social-publishing\ndescription: Draft, schedule, and publish social posts through Magister, and read post and follower analytics. Use when the user wants to write a social post in their brand voice, schedule content, publish a draft, see how posts performed, or find the best time to post.\n---\n\n# Social posts through Magister\n\nDrafting and scheduling are ordinary writes. **Publishing to a public account\nrequires a person's approval** and cannot be forced from this connector.\n\nResolve `project_id` from `list_projects` first; never guess one.\n\n## Every post needs a real account\n\nCall `list_social_accounts` before creating a post. Each platform you post to\nneeds its **`account_id` from that list** — supplying a platform name alone is\nrejected. Do not invent an account id and do not carry one over from a previous\nconversation.\n\nIf several accounts are connected for a platform, ask which one.\n\n## Drafting\n\n`create_social_post` creates a draft. Read `get_brand` first so the copy matches\nthe brand's actual voice, audience, and messaging pillars rather than a generic\ntone.\n\n`update_social_post` edits an unpublished post. Note that it **overwrites the\ncaption with no revision history**, so if the user may want the previous version,\nshow it to them before replacing it.\n\n## Scheduling commits to a future public post\n\nSupplying a schedule time is not the same as saving a draft. Once approved, the\npost will publish publicly at that time, and **this connector has no tool to\nunschedule or delete it afterwards** — that has to be done in the Magister app.\n\nSay that before scheduling, and confirm the time and time zone.\n\n## Publishing requires approval, and that is not a failure\n\n`publish_social_post` does not publish on the call. It creates a permission\nrequest describing the exact post, and a person must approve it in the Magister\napp before anything goes live.\n\nWhen the tool returns that it needs approval:\n\n- Tell the user the post is waiting for their approval and give them the\n approval link the tool returned.\n- **Do not call the tool again.** A second call does not publish it and only\n creates confusion; the request is already waiting.\n- Do not describe the post as published, live, or sent.\n- `get_action_approval` checks one request's status and\n `list_action_approvals` lists pending ones, if the user asks what is waiting.\n\n## Reading performance\n\n`list_social_posts` returns the project's posts and their status.\n`get_social_analytics` returns per-post metrics, daily numbers, follower stats,\nand best-time-to-post insights for the connected accounts.\n\nUse the posting-time data when the user asks when to post, rather than offering\ngeneric advice about optimal posting times.\n\n## Do not infer\n\n- Never state engagement, reach, or follower numbers the tools did not return.\n- Never claim a post published without a completed publish.\n- Never work around the approval step, even if the user asks you to skip it.\n"
}SHA-256: 805922e4639a4aa64ae481b5d358fa5db558929c2a48b137342e99c579ef4dd2