Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Parse raw WhatsApp exports (TXT or JSON) into normalized message objects with `timestamp`, `sender`, and `content`. Use when users ask to parse chat export,...
Parse raw WhatsApp exports (TXT or JSON) into normalized message objects with `timestamp`, `sender`, and `content`. Use when users ask to parse chat export,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Convert raw chat exports into a strict array of parsed message objects.
Parse this WhatsApp export file. Convert this group dump into structured messages. Clean this TXT chat into timestamp/sender/content rows.
message-parser -> lead-extractor -> india-location-normalizer -> sentiment-priority-scorer -> summary-generator -> action-suggester -> lead-storage
Accept raw WhatsApp export input as plain text, JSON, or file contents already loaded by Supervisor. Detect and parse the source format, including WhatsApp export lines like DD/MM/YYYY, HH:MM - sender: message. Normalize each event into exactly three fields: timestamp (RFC 3339 date-time string) sender (non-empty string) content (string; allow empty message bodies) Merge multiline continuation lines into the previous message when they do not start with a new timestamp marker. Preserve message ordering. If timestamps collide, preserve original source order. Ignore chat-system boilerplate as lead content (encryption notice, group created, member added) while preserving raw line fidelity for audit. Validate output against references/parsed-message-array.schema.json. Return only the validated array.
Never infer or extract leads. Never write to databases or files. Never generate summaries or action plans. Never send or schedule outbound communication. Never bypass Supervisor routing.
Return explicit parse errors for malformed entries. Include line offsets when source lines are available. Fail closed if output cannot satisfy the schema.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.