Open-source skills that teach your AI to triage the inbox, brief you before a call, chase what went quiet, and watch your numbers. Seven live today, seven landing shortly.
Every skill is a single markdown file your agent reads. Nothing runs on our servers, and each card tells you upfront whether it only reads, changes things inside your workspace, or messages customers.
Scan a QR code to connect your number, then install whichever skills you want. No WhatsApp Business API, no developer, no Meta approval.
These skills operate the same workspace those teams use every day — same inbox, same permissions, same quota.
“We connected 12 WhatsApp numbers to one shared inbox and the CRM sync just works. Setup took about 3 minutes — no API keys, no developer needed.”
“Before TimelinesAI we were losing conversations across 5 different phones. Now every message is logged in HubSpot automatically and the team can pick up any chat without context loss.”
“The mass messaging feature alone paid for itself in the first week. We send personalized broadcasts to 2,000+ contacts and every reply lands right in the shared inbox.”
A single markdown file — a SKILL.md — that your AI reads before doing a task. It carries the recipe, the safety rules, and the things that go wrong. Your agent already has the reasoning; the skill supplies the WhatsApp know-how, so you ask in plain English instead of explaining the API every time.
It depends which skill. Ones badged MCP ride on the MCP connector, which uses OAuth — you sign in once and there's no key to generate or rotate. Ones badged API call the TimelinesAI public API and need a token from Integrations → Public API. The trade-off: API skills can run unattended on a schedule or a webhook, MCP skills only run when you ask.
Inbox triage, if you have a shared inbox that gets messy. Account brief, if you mostly want context before calls — it only reads, so there's nothing to undo. Both are MCP skills, so if you've already added the connector there's no extra setup at all.
Only the four badged Sends to customers, and you choose whether to install them. Everything else either only reads, or changes things inside your workspace — labels, assignment, private notes — which a teammate can undo. The skills that do send are built to reply inside conversations a customer started, never to start new ones, and they refuse to run on chats you've labelled hands-off. Sends are real and immediate: there is no sandbox and no undo.
Yes, and you should. Every skill is one readable markdown file on GitHub under an MIT licence — no build step, no binary, nothing hidden. Each card links straight to its repo. If a rule in there doesn't suit your team, edit it; they're meant to be forked.
Yes. TimelinesAI connects your existing personal or business WhatsApp by QR code, with no Meta approval process. WABA numbers work too. Worth knowing: WhatsApp bans personal numbers for cold outreach and broadcasts, so the outbound skills here are deliberately limited to transactional and reply-style messages.
A TimelinesAI account with at least one WhatsApp number connected, plus either the MCP connector or an API token depending on the skill. These operate a real inbox rather than a demo environment, so without a connected number most of them return nothing.
Longer reads on advanced WhatsApp integrations, automation, and picking the right connection method for your business.
How OpenClaw skills automate WhatsApp workflows — from lead qualification to customer support at scale.
Read guide ↗ AI IntegrationHow to use the Model Context Protocol to connect WhatsApp conversations directly to AI agents and LLMs.
Read guide ↗ Best PracticesThe three WhatsApp connection methods compared side by side, and which fits your sales stack.
Read guide ↗Start your 10-day free trial today. No credit card required, and setup takes under 2 minutes.
