v2.0.0

Competitor Monitor

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 8:11 AM.

Analysis

This skill matches its stated price-monitoring purpose, but it can run on a schedule, store local history, and post alerts through user-configured webhooks.

GuidanceThis appears safe to install if you want scheduled competitor price monitoring. Before enabling it, protect any webhook or email credentials, confirm the monitored data is accurate for your platforms, understand that alerts may be sent to external chat services, and remove the cron job if you no longer want it running.

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.

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.

Human-Agent Trust Exploitation

SeverityLowConfidenceMediumStatusNote

SKILL.md

A: 价格 100% 准确，销量为估算（误差±20%）。

The documentation makes a strong accuracy claim, while other included artifacts describe demo or simulated data for some platforms, so users should not over-trust the output without validation.

User impactA user could make pricing decisions based on data that may be incomplete, simulated, or platform-limited.

RecommendationVerify monitored prices against the original platform or official APIs before making important pricing changes.

Rogue Agents

SeverityLowConfidenceHighStatusNote

SKILL.md

openclaw cron add competitor-monitor --interval 30

The instructions include adding a recurring scheduled task every 30 minutes.

User impactIf the user adds the cron job, the monitor can keep running and making network checks after the initial setup.

RecommendationOnly enable the cron schedule if continuous monitoring is desired, and remove or disable it when no longer needed.

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

config/notify.json

"webhook": "" ... "password": ""

The notification configuration has fields for webhook URLs and an email password, which are credentials or delegated posting secrets.

User impactAnyone with access to the filled configuration file may be able to use or misuse the configured notification credentials.

RecommendationKeep notification configuration files private, use least-privilege webhooks, and avoid committing real webhook URLs or email passwords.

Sensitive data protection

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

Insecure Inter-Agent Communication

SeverityLowConfidenceHighStatusNote

scripts/monitor_v2.py

response = requests.post(webhook_url, json=data, headers=headers, timeout=10)

The script sends generated alert messages to user-configured WeChat or DingTalk webhook endpoints.

User impactProduct names, prices, and monitoring alerts can be sent to external chat services when notifications are enabled.

RecommendationUse trusted webhook endpoints and review alert contents before enabling notifications for sensitive product watchlists.

Memory and Context Poisoning

SeverityInfoConfidenceHighStatusNote

scripts/monitor_v2.py

history = history[-100:]
with open(history_file, "w", encoding="utf-8") as f:
    json.dump(history, f, ensure_ascii=False, indent=2)

The script stores recent price history locally and reuses it to detect future price changes.

User impactLocal history files may reveal monitored competitors and can affect future alerts if edited or corrupted.

RecommendationReview and protect the output/history directory, and clear old history if you no longer want the watchlist retained.