← TimelinesAI for WhatsAppCONTENT HISTORY
WHAT CHANGED
Update to TimelinesAI for WhatsApp
Snapshot Nov 3, 2026 · 18:39 UTC · version 1.0.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save TimelinesAI for WhatsApp and check future changes in Following.
Up to 5 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Sweep the user's TimelinesAI WhatsApp inbox and report which chats need attention. Use when the user asks what needs them today, who is waiting for a reply, which chats are unread, urgent or stalled, or wants a morning briefing of their WhatsApp chats.",
"included_files": [],
"name": "inbox-triage",
"skill_md_contents": "---\nname: inbox-triage\ndescription: Sweep the user's TimelinesAI WhatsApp inbox and report which chats need attention. Use when the user asks what needs them today, who is waiting for a reply, which chats are unread, urgent or stalled, or wants a morning briefing of their WhatsApp chats.\n---\n\nUse this skill to answer \"what needs me?\" across the user's WhatsApp numbers. This workflow only reads. It never sends, labels, assigns or closes anything.\n\n1. Call `workspace_whatsapp_accounts` to see the connected numbers. If the user named a number, teammate or label, pass it as a filter (`whatsapp_account_id`, `responsible` with the teammate's email from `workspace_team`, or `labels`). Otherwise cover all numbers.\n2. Call `list_chats` with `closed` set to false. Run it once with `read` set to false for unread chats, and once without `read` for open chats in general. Results come 50 per page; continue with `page` only while `has_more_pages` is true and the user wants the full picture. `list_chats` cannot filter by last activity, only by creation date, so the waiting time must come from the messages.\n3. For each chat that could need attention, call `chat_history` and read only the most recent messages. Use `from_me` to tell our messages from the customer's. Do not read whole histories. When there are many chats, work through the unread ones first and tell the user how many you covered and how many you did not.\n4. Sort what you read into three lists, most urgent first:\n - Waiting on us: the customer's message is the latest and nobody has replied.\n - Stalled: we wrote last, after a question or promise, and the customer has been quiet for 2 or more days.\n - Unassigned: open chats with no teammate. `list_chats` cannot filter for this, so check `chat_details` for chats you are already reporting on and do not try to scan the whole inbox for it.\n5. For each chat give the contact or group name, the number it came in on, the owner, how long it has waited (from the message timestamps), and a one-line reason, quoted or paraphrased from the actual messages.\n6. If WhatsApp Business API numbers are connected (`waba_accounts`), run `waba_list_chats` with `closed` set to false and `with_msg` set to true, and report them in a separate section.\n7. End by offering next steps, such as drafting replies, assigning or labelling. Do not take them unasked.\n\nDo not guess urgency from a contact's name. Base it only on message content and waiting time. If a tool returns no chats, say so plainly instead of filling the list.\n"
}SHA-256 of public snapshot: 23182aed1e2ca18cc77160d4c5d08ede6ea5ef7aa73fb272166552cb9f73d237