← DunSocialCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to DunSocial
Snapshot Sep 30, 2026 · 23:11 UTC · version 1.1.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
{
"description": "Create, validate, schedule, and publish DunSocial content across connected social accounts and messaging channels.",
"included_files": [],
"name": "dunsocial-social-publishing",
"skill_md_contents": "---\nname: dunsocial-social-publishing\ndescription: Create, validate, schedule, and publish DunSocial content across connected social accounts and messaging channels.\n---\n\n# DunSocial social publishing\n\nUse this skill when a user wants to create content, validate it, schedule it, publish it, or manage connected social destinations through DunSocial.\n\n## Workflow\n\n1. Use `list_workspaces` and `get_workspace` when workspace context is unclear.\n2. Use `list_social_accounts` before choosing a destination account.\n3. Call `validate_post` before `schedule_post` or `publish_now`. If validation returns `valid: false`, follow each `issues[].next` instruction and validate again.\n4. For Discord, call `list_discord_channels` first, then use `schedule_discord_post` or `publish_discord_now` with a returned channel ID.\n5. For Slack, call `list_slack_channels` first, then use `schedule_slack_post` or `publish_slack_now` with a returned channel ID.\n6. For Pinterest, use `list_pinterest_boards`; if no suitable board exists, use `create_pinterest_board` before publishing.\n7. For media, use `get_upload_url` and `complete_upload`, then reference the resulting media in the post.\n8. Treat `publish_*` results as the only confirmation that external content was published. A draft or scheduled result is not a publication confirmation.\n\n## Safety\n\n- Ask for confirmation immediately before any publish or delete action when the user has not clearly requested it.\n- Never claim content is live unless the corresponding publish tool returns a successful queued or published result.\n- Do not retry write operations after a subscription-required response; report the returned access message and billing URL.\n- Use dedicated platform tools for Reddit, Instagram, TikTok, Pinterest, Discord, and Slack when available.\n"
}SHA-256 of public snapshot: 1a75a9217ddff43f0e4cb413e8ba5c9c5d4389a621339c22a423fdc4ac779377