Back to skill
v1.0.0

Dada

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

Analysis

This is a coherent instruction-only developer guide for Dada delivery API integration, with expected notes around live order APIs, API secrets, and delivery personal data.

GuidanceThis skill appears safe as an instruction-only Dada API reference. Before using it with production systems, keep API secrets out of chat and logs, test against the QA endpoint, require explicit approval for live order creation or cancellation, and redact customer/courier personal data from logs.

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.

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
SeverityMediumConfidenceHighStatusNote
SKILL.md
接口:`/api/order/addOrder` ... 接口:`/api/order/formalCancel`

The skill documents APIs that can create and cancel real delivery orders. This is purpose-aligned, but these operations can affect customers, couriers, fees, and business records if used against production.

User impactIf connected to real credentials and network tools, mistakes could create or cancel live delivery orders.
RecommendationUse the test endpoint first, require explicit confirmation before production order creation or cancellation, and verify all order details before sending requests.
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 签名认证机制:app_key + app_secret + timestamp 签名

The skill expects use of Dada API credentials for request signing. This is normal for the stated integration purpose, but the registry metadata does not declare a credential contract because the skill is instruction-only.

User impactUsers may need to provide API keys or secrets while following the guide, and mishandling those secrets could expose account access.
RecommendationDo not paste production secrets into shared chats or logs; store app_secret in a secure secret manager or environment variable and rotate it if exposed.
Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning
SeverityMediumConfidenceHighStatusNote
SKILL.md
记录所有 API 请求和响应日志,便于排查问题

The guide recommends logging all API requests and responses. Since the documented request fields include recipient names, phone numbers, addresses, coordinates, and signatures, full logs could retain sensitive delivery data unless redacted.

User impactDebug logs could accidentally store customer or courier personal data and request authentication material.
RecommendationLog only what is necessary, redact phone numbers, addresses, signatures, and identifiers, and set clear retention and access controls for logs.