v1.0.0

Wework

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 7:08 AM.

Analysis

This is an instruction-only Enterprise WeChat API guide; it does not install or run code, but it describes credentials and APIs that can change or message an organization.

GuidanceThis skill appears safe as an instruction-only API reference. Before using it with a real Enterprise WeChat tenant, protect corpsecret values and access tokens, use least-privilege API permissions, and require review before deleting data, changing contacts, submitting approvals, or sending broad messages.

Findings (2)

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.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

SKILL.md

删除部门：`GET /cgi-bin/department/delete?id=ID` ... 发送应用消息：`POST /cgi-bin/message/send` ... `"touser": "@all"`

The skill documents mutating and broadcast-capable Enterprise WeChat API operations. This is expected for a developer assistant, but these operations could affect many users if implemented with real credentials.

User impactIf a user follows the API guidance with live credentials, they could delete or modify organizational data or send messages to many employees.

RecommendationUse test environments first, require human approval for destructive or broadcast actions, and limit message recipients and API scopes.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

SKILL.md

企业微信 API 基于 corpid + corpsecret 获取 access_token，不同 secret 对应不同权限范围

The skill explains the use of Enterprise WeChat secrets and access tokens, including secrets for address book and customer-contact access. This is purpose-aligned, but those credentials can grant sensitive enterprise permissions.

User impactLeaked or over-scoped secrets could allow unauthorized access to company contacts, customer data, or messaging functions.

RecommendationUse the least-privileged secret needed, avoid pasting secrets into prompts or logs, rotate exposed credentials, and store tokens in a secure secret manager.