qywx-notify

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill appears to send WeCom notifications as advertised, but it can expose the private webhook token in logs or configuration output.

Install only if you are comfortable with a skill that can post to WeCom group chats. Before using it, patch or verify webhook redaction so the full webhook URL is not logged or returned, and keep the webhook limited to the minimum necessary chat permissions.

Findings (3)

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.

What this means

Anyone who can see agent logs, command results, or configuration output may obtain the full webhook URL and use it to send messages to the WeCom group.

Why it was flagged

this.config can include defaultWebhook, and params can include webhook, so full webhook credentials may be written to logs or returned even though only a masked value is needed.

Skill content
this.log(`Skill initialized with config: ${JSON.stringify(this.config, null, 2)}`); ... case 'config': return { success: true, config: this.config, maskedWebhook: ... }; ... request: params
Recommendation

Do not log full config or return raw params containing webhooks. Return only masked webhook values, redact defaultWebhook from config output, and avoid echoing the webhook on errors.

What this means

A mistaken or autonomous invocation could send an unwanted message or notify an entire group.

Why it was flagged

The skill can post agent/user-supplied content into a group chat and optionally mention everyone; this is aligned with the purpose but can be disruptive if invoked unintentionally.

Skill content
Send notifications to group chats via WeCom robot Webhook ... ✅ @all mention support
Recommendation

Use this skill only with trusted workflows, review message content before sending important announcements, and restrict who can access the webhook.

What this means

A future install may fetch a different compatible axios version than the one originally tested.

Why it was flagged

The runtime dependency is installed from npm using a caret version range, and the provided manifest does not include a lockfile.

Skill content
"dependencies": { "axios": "^1.6.0" }
Recommendation

Pin exact dependency versions and include a lockfile or verified install process.