← MallaryCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Mallary
Snapshot Sep 30, 2026 · 22:58 UTC · version 1.0.2
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": "mallary-comment-engagement",
"description": "Use when the user explicitly asks to list, draft, or post replies to comments on posts published through Mallary.",
"included_files": [],
"skill_md_contents": "---\nname: mallary-comment-engagement\ndescription: Use when the user explicitly asks to list, draft, or post replies to comments on posts published through Mallary.\n---\n\n# Mallary Comment Engagement\n\nUse this skill only for comments connected to the user's Mallary posts.\n\n## Read Comments\n\n1. Use `mallary_list_posts` if the Mallary post ID is not known.\n2. Use `mallary_list_comments` with the exact `post_id`.\n3. Return only the comment details needed for the user's request.\n\nDo not invent a post ID, comment ID, platform, author name, or username. Some platforms may not return every author field.\n\n## Draft and Post a Reply\n\n1. Draft the reply in the voice and tone the user requested.\n2. Show the exact post ID, comment ID, original comment context, and reply text.\n3. State that the reply will be posted publicly to the connected social platform.\n4. Wait for clear user confirmation.\n5. Call `mallary_reply_to_comment` once with the exact returned IDs.\n\nNever post a draft automatically. Never silently retry a reply after a timeout or unclear result. Check comments first, then ask the user before another write.\n\n## Privacy\n\nTreat comment text and author details as account data. Show only what the user needs. Never expose OAuth tokens, social account credentials, API keys, provider debug data, or unrelated comments.\n"
}SHA-256: ae4fa54e11ce9ced00f4fcd6d5b04afe0ea1879f12c2fc1b08b1e528f92f4741