Sentiment Tracker
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: sentiment-tracker Version: 1.0.0 The skill is designed for local sentiment analysis, explicitly stating that all tracking data is stored locally in `~/sentiment-analysis/` and no data is stored externally or personal information sent anywhere. Network access is limited to `web_search` and `web_fetch` for public content, consistent with the stated purpose. While the skill instructs the agent to use `cron` for scheduled monitoring, this is a legitimate function for a tracking skill and is not used for malicious persistence. Instructions to the agent regarding communication style (e.g., not revealing internal file operations) are aimed at improving user experience and do not hide any malicious actions.
Findings (0)
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.
Your searched entity names, keywords, and visited public-post URLs may be sent to search or web-fetch providers.
The skill discloses use of external web search and fetch tools to gather public mentions, which is expected for sentiment tracking but means search queries and URL requests leave the machine.
| Search engines (via web_search) | Query text | Find mentions |
Use this only for topics you are comfortable searching publicly, and avoid putting private or confidential terms into monitored keywords.
Tracking preferences and activation choices may persist across sessions and influence when the skill is used later.
The skill asks the agent to store user preferences in persistent memory for future sessions. This is useful for monitoring, but persistent memory can affect future agent behavior.
Save their answer to their MAIN memory so other sessions know when to activate this skill.
Confirm what gets saved, periodically review the sentiment-analysis memory files and main memory, and remove or pause monitoring entries you no longer want.
If enabled, the skill may keep checking sentiment and producing alerts on a schedule.
The skill supports scheduled recurring monitoring. This is disclosed and matches the product purpose, but scheduled work is persistent behavior that can continue after setup.
For ongoing tracking, use cron. Default schedules: - **Critical entities**: Daily at 09:00 - **Regular entities**: Every 3 days - **Background entities**: Weekly
Only enable scheduled monitoring after confirming the entities, frequency, alert thresholds, delivery channel, and how to pause or remove the schedule.