glass2claw
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent photo-routing template, but it needs review because it can automatically forward personal WhatsApp photos to other sessions/channels and write database records, with broad sample triggers.
Before installing, treat this as a template rather than a turnkey safe workflow. Only use private WhatsApp/OpenClaw ingress channels, require verified WhatsApp-origin markers, allowlist destination sessions, use least-privilege database tokens, and add confirmation or rollback for database writes and Discord posts involving sensitive photos.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A wrongly routed, accidental, or untrusted image URL could be sent to specialist agents or channels without another check.
The sample turns a broad image-URL match into automatic cross-session tool use; a bare URL is weak origin verification for forwarding personal images.
look for `[Ingress:WhatsApp]` prefix or a bare image URL... Immediately classify... Forward using `sessions_send`
Require a verified WhatsApp ingress marker or trusted sender, restrict the hub channel, allowlist session keys, and require confirmation for unrecognized sources or ambiguous categories.
A misclassified photo or crafted message could create persistent records or posts in the wrong destination before the user reviews it.
The workflow chains classification, forwarding, and database mutation automatically, so one mistaken input or classification can propagate into other sessions and storage.
Everything downstream is automatic... routes to the matching specialist agent... writes structured entry to your database
Add audit logs, confirmation for new destinations, conservative handling for ambiguous/private items, and an easy delete or rollback process.
Over-scoped credentials could let the agent access or modify more content than intended.
The workflow depends on WhatsApp session access and database API credentials; this is expected for the integration but sensitive.
OpenClaw with WhatsApp channel... Destination databases... Database credentials — set up API access for your chosen database yourself
Use dedicated, least-privilege API tokens and private WhatsApp/OpenClaw channels; avoid broad workspace tokens.
Personal photos, faces, business cards, or labels may be stored or displayed in third-party services such as Discord, Notion, or Airtable.
Personal image data is intentionally passed through multiple services and agent sessions, so privacy depends on destination configuration.
Images flow from WhatsApp → your OpenClaw instance → your configured destination. Any external services you connect (Notion, Discord, etc.)...
Use private destination channels and databases, verify retention/privacy settings, and do not route sensitive photos unless intended.