fugui-monitor
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill mostly matches its monitoring purpose, but it hard-codes a Feishu recipient while using persistent browser login state for recurring monitoring.
Review the script before enabling cron. Replace the hard-coded Feishu target with your own recipient, consider using a dedicated Xiaohongshu/OpenClaw browser profile, and periodically check or remove the stored logs and snapshots.
Findings (4)
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.
Alerts could be sent from the user's environment to a pre-set Feishu account rather than the installer’s intended recipient.
The skill says it sends Feishu notifications to the user, but the script sends via the user's messaging capability to a fixed recipient ID that is not shown as configurable.
"$OPENCLAW" message send ... --target "ou_24c2bc2b000e0ea7a99dea7f4f657dbc" --message "$msg"
Before using, replace the Feishu target with your own recipient or make it configurable, and verify who can receive the messages.
The monitor will rely on your Xiaohongshu login session, which is sensitive account state even though it is expected for this workflow.
The skill requires a persistent logged-in Xiaohongshu browser profile/cookie state so it can monitor pages.
首次使用需要在浏览器中登录小红书一次，之后脚本会自动使用登录态
Use a dedicated OpenClaw browser profile or account if possible, and only install if you are comfortable with the script using that session.
If you configure cron, the skill can continue checking Xiaohongshu and sending notifications without further prompts.
The skill is intended to run repeatedly on a schedule, creating ongoing monitoring behavior.
08:00-18:00 每5分钟，18:00-24:00 每10分钟，00:00-08:00 不监控
Confirm the cron schedule yourself and remove only this skill’s scheduled entries when you no longer want monitoring.
Monitored post titles and run logs remain on disk for duplicate detection and troubleshooting.
The script persists logs and post snapshots under the OpenClaw workspace memory directory.
LOG_FILE="$WORKSPACE/memory/$log_file" ... > "$WORKSPACE/memory/$snapshot_file"
Review or delete the memory files if you do not want this monitoring history retained.