From zalo
Authenticate or log in to Zalo personal account. Use when the user says "connect Zalo", "log in to Zalo", "scan QR", "zalo auth", or when a tool errors with "Zalo not logged in".
How this skill is triggered — by the user, by Claude, or both
Slash command
/zalo:authThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Call the `zalo_login` tool now. Read the QR image at the returned path, show it to the user, and tell them:
Call the zalo_login tool now. Read the QR image at the returned path, show it to the user, and tell them:
Open Zalo app → More → QR scan → scan the code → confirm on your phone (within ~100 seconds).
Login finishes in the background; credentials save automatically and are account-global (one scan
works across every project, survives restarts). Confirm success with zalo_status or by sending/
receiving a message.
To answer Zalo, the session must be launched with the dev-channel flag — otherwise inbound notifications are silently dropped (outbound still works, which masks the cause):
claude --dangerously-load-development-channels plugin:zalo@imrim12
The proxy reads this flag off the launching claude process and auto-enables inbound for that
session. Override with ZALO_INBOUND=1 (force on) / ZALO_INBOUND=0 (force off) only for unusual
launches. If inbound seems dead, run zalo_status.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub imrim12/claude-plugin-zalo --plugin zalo