| name | channel-access |
| description | Use local read-only iMessage, WhatsApp, and LinkedIn channel access wrappers for raw message discovery, sample exports, and CRM provenance workflows. |
| metadata | {"openclaw":{"category":"productivity","requires":{"bins":"[Truncated]"}}} |
Channel Access
Use this skill when a task needs local iMessage, WhatsApp, or LinkedIn context from the
developer's private channel stores, including CRM updates, relationship context,
meeting logistics, follow-up reconstruction, or raw procedural discovery.
Security Rules
- Default to read-only access.
- Do not send, edit, delete, forward, explicitly mark-read, mutate
contacts/groups, connect, react, follow, endorse, archive, or otherwise write
to channels unless the user explicitly approves that action and the relevant
write-enable mechanism is intentionally set for that call.
- For LinkedIn v1, no write paths are implemented. Bounded message-thread opens
may incidentally mark conversations read when the user has approved that
workflow; do not perform explicit read/unread state changes.
- Do not paste full raw private threads into task artifacts, Notion, GitHub,
Linear, public logs, or cloud tools.
- Use bounded searches/windows by default.
- Save full raw validation samples only under
~/pro/lab/zone-channel-ingest/samples/.
- Let wrapper query audit logs record command arguments/counts; do not create
extra message-content logs unless the user asks.
State
Private state lives under:
~/pro/lab/zone-channel-ingest/
Main labels:
- iMessage:
imessage-sourya-mac
- WhatsApp:
whatsapp-sourya
- LinkedIn:
linkedin-sourya
Config:
~/pro/lab/zone-channel-ingest/config/channel-ingest.env
The canonical personal-channel collector is the private GCP host
research-cpu-01-ts (research-cpu-01). The wrappers route WhatsApp and
LinkedIn commands there automatically from other configured agent contexts.
iMessage reads route to the live sourya-mac database when invoked from Linux;
on the Mac they read locally. Set ZONE_CHANNEL_EXEC_LOCAL=1 only inside the
resolved backend host to suppress another routing hop.
Health
Start with:
channel-health
This reports the current machine's installed versions, private store paths,
disk usage/cap, WhatsApp auth status, iMessage database state, and LinkedIn
browser state paths. For an authoritative multi-source check, also run one
bounded command per source because each wrapper resolves its canonical host:
channel-imessage-read chats --limit 1 --json
channel-whatsapp-read chats list --limit 1
channel-linkedin-health
WhatsApp
Read-only examples:
channel-whatsapp-read auth status
channel-whatsapp-read chats list --limit 20
channel-whatsapp-read messages list --limit 20
channel-whatsapp-read messages search "query" --limit 20
channel-whatsapp-read messages context --chat JID --id MSG_ID --before 5 --after 5
On-demand sync:
channel-whatsapp-sync sync --once --idle-exit 30s --refresh-contacts --refresh-groups
Pairing is an interactive human step:
channel-whatsapp-auth --phone "+15551234567"
Do not run pairing or sync with broad history/backfill options unless the task
requires it and the storage cap has been checked.
research-cpu-01-ts is the only WhatsApp sync writer. Do not run a second
collector on the retired Azure host or another machine. Reads remain forced
read-only even when invoked from another context.
iMessage
Normal reads use the live sourya-mac database, including when invoked from
Linux through the routing wrapper:
channel-imessage-read chats --limit 20 --json
channel-imessage-read search --query "query" --limit 20 --json
channel-imessage-read history --chat-id ID --limit 50 --json
Pull a copied database to the current Linux host only as a fallback snapshot:
channel-imessage-pull
Copy attachments too only when the task needs media and storage has been
reviewed:
channel-imessage-pull --with-attachments
Linux imsg is read-only for a copied macOS chat.db; it is not a live
iMessage client and cannot send messages.
LinkedIn
LinkedIn access uses a dedicated VM Chrome profile plus Playwright browser
automation. It is read-only by construction in v1.
Human login from the research-cpu-01-ts GUI/remote desktop terminal:
channel-linkedin-login
Read-only examples:
channel-linkedin-health
channel-linkedin-read recent --limit 20 --open-limit 10 --max-messages 50
channel-linkedin-read thread --thread-url "https://www.linkedin.com/messaging/thread/..." --max-messages 50
channel-linkedin-read thread --profile-url "https://www.linkedin.com/in/example/" --max-messages 50
channel-linkedin-read thread --name "Person Name" --max-messages 50
channel-linkedin-read profile --thread-url "https://www.linkedin.com/messaging/thread/..." --experience-limit 3
channel-linkedin-read profile --profile-url "https://www.linkedin.com/in/example/" --experience-limit 3
Rules:
- Keep LinkedIn raw outputs private under
~/pro/lab/zone-channel-ingest/.
- Do not paste full raw LinkedIn threads into task artifacts, Notion, GitHub,
Linear, or cloud tools.
- Do not implement or invoke LinkedIn sends, connection requests, reactions,
follows, archives, deletes, or broad profile scraping from this skill.
- Prefer bounded recent-inbox scans and explicit user-provided profile/thread
targets.
- Profile parsing v1 is limited to CRM-relevant visible fields: name, headline,
location, profile URL, about snippet, company/profile URLs, and a small recent
experience window. Do not pull education, skills, posts/activity, or full
history unless separately approved.
Samples
Write full samples privately:
channel-sample whatsapp
channel-sample imessage chats --limit 20 --json
channel-sample imessage history --chat-id ID --limit 50 --json
channel-linkedin-sample recent --limit 5 --open-limit 2 --max-messages 20
channel-linkedin-sample thread --thread-url "https://www.linkedin.com/messaging/thread/..." --max-messages 50
channel-linkedin-sample thread --profile-url "https://www.linkedin.com/in/example/" --max-messages 50
channel-linkedin-sample profile --thread-url "https://www.linkedin.com/messaging/thread/..." --experience-limit 3
After creating a sample, summarize only metadata in task artifacts unless the
user explicitly asks to promote content.
Troubleshooting
- If
channel-imessage-pull fails, check SSH access to sourya-mac, remote
sqlite3, and macOS Full Disk Access/TCC behavior. Do not install a Mac-side
LaunchAgent without explicit user approval.
- If a Linux
channel-imessage-read fails before reaching the Mac, check its
SSH alias and sourya-mac Full Disk Access first. Swift runtime troubleshooting
applies only to the copied-database fallback.
- If
wacli commands fail on locks or auth, use channel-health and
channel-whatsapp-read auth status before retrying.
- If
channel-linkedin-health reports login_required_or_not_verified, run
channel-linkedin-login from a research-cpu-01-ts GUI/remote desktop
terminal and complete LinkedIn login manually.
- If LinkedIn selectors fail, keep the raw failure private and update the
Playwright extractor rather than broadening scans or using private APIs
without fresh user approval.
