Public Skill
ReviewAudited by ClawScan on May 10, 2026.
Overview
This skill appears to match its stated purpose of sending plain-text messages to the user’s own bound email, but it relies on the user’s logged-in OpenClaw/platform session and can read user-selected files for email content.
Before installing, confirm you want this skill to use your OpenClaw/platform login to send plain-text messages to your own bound email. Review the subject, body, recipient, and any --subject-file or --body-file paths before sending, and avoid using it for secrets or third-party recipients.
Findings (5)
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.
The skill can use the logged-in platform context to query the bound email, send mail through the platform channel, and participate in email binding flows.
The router is designed to call platform APIs through an authenticated local gateway, which means it operates using the user's OpenClaw/platform session even though it does not directly handle a token.
通过 Auth Gateway 代理访问 jprx.m.qq.com 平台接口
Use it only for messages you intend to send to your own bound mailbox, and do not share verification codes or account credentials with the agent.
Message subjects, bodies, and binding-related data may be processed by the local Auth Gateway and the platform email service.
Email and binding requests are sent through a localhost gateway to the remote platform endpoint, so email content and the bound address cross a provider/gateway boundary.
host: '127.0.0.1', port: Number(proxyPort), path: '/proxy/api', method: 'POST', headers: { 'Remote-URL': `${REMOTE_BASE_URL}${apiPath}`Avoid sending secrets or highly sensitive content unless you are comfortable with that data passing through the platform email gateway.
If an agent or user points --body-file or --subject-file at a sensitive local file, that file's text may be sent as email content.
The router can read subject/body content from a user-supplied file path. This is expected for file-based email bodies, but it can disclose local file contents if the wrong path is chosen.
const resolvedPath = path.resolve(process.cwd(), filePath); ... return fs.readFileSync(resolvedPath, 'utf8');
Review any file path used for email content before sending, and prefer inline text for sensitive workflows.
The skill runs local Node code and may spawn a local helper command during gateway setup.
The router includes local process execution for WSL proxy-port detection. The visible command is fixed and not user-controlled, but static scanning also reports a child_process spawn helper in the truncated portion of the router.
const port = await runProcess('cmd.exe', ['/C', 'echo %AUTH_GATEWAY_PORT%'], { allowFailure: true });This is not inherently unsafe here, but install only from a publisher you trust and keep the reviewed code available.
Users have less external provenance information to verify the skill and may not be warned up front that Node is needed.
The registry metadata does not identify a source repository or homepage, and it under-declares the Node runtime required by the included shell wrapper.
Source: unknown; Homepage: none; Required binaries (all must exist): none
Review the included scripts before installation and ensure Node is expected in your OpenClaw environment.