← Ciarem AICONTENT HISTORY
WHAT CHANGED
Update to Ciarem AI
Snapshot Oct 24, 2026 · 13:42 UTC · version 0.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Ciarem AI and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user asks what needs their attention in Ciarem, which customers are waiting, or wants help catching up on their inbox.",
"included_files": [],
"name": "inbox-triage",
"skill_md_contents": "---\nname: inbox-triage\ndescription: Use when the user asks what needs their attention in Ciarem, which customers are waiting, or wants help catching up on their inbox.\n---\n\n# Inbox triage\n\n1. Call `list_conversations` with `status: \"open\"` and `assigned_to_me: true` (limit 25). If the user is an admin and asks about the whole team, also call it with `unassigned: true`.\n2. Rank by who has waited longest: `last_inbound_at` older than `last_message_at` of our reply, oldest first, then `unread_count`.\n3. For the top 5, call `get_conversation` (limit 15) and write one line each: who, channel, what they want, how long they've waited.\n4. Under each line, draft a short reply in the customer's language and tone. Say it is a draft: Ciarem's tools can't send messages from here. Link the conversation's `url` so the user can send it from Ciarem.\n5. Skip conversations `handled_by: \"ai\"` unless the customer asked for a human; mention how many the AI is covering.\n\nNever invent order numbers, prices or policies in a draft. If the answer needs a fact, call `search_knowledge` first; if it isn't there, say the draft needs that fact filled in.\n"
}SHA-256 of public snapshot: 62cd3f38c8c8705493ddaa04b3ee8a92aaa91693172205182435ee569c4a26bd