Social Listening Monitoring

Monitor brand mentions across Twitter/X, Reddit, news, and forums in real-time with sentiment analysis, crisis detection, competitor tracking, and instant al...

This skill appears to implement a real social-listening workflow, but the SKILL.md requires multiple API keys/webhooks that are not declared in the registry metadata. Before installing: (1) Confirm the skill's source and a homepage or repository (the package lists 'unknown'); (2) Ask the publisher to update the manifest to explicitly declare required env vars (APIFY_TOKEN, CLAUDE_API_KEY, SLACK_WEBHOOK_URL, TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID, etc.) so you can review permissions up front; (3) Never paste real production keys into example text — instead use scoped/test tokens first; (4) Review the Apify actors being called (apify/twitter-scraper, reddit-search-scraper, etc.) to understand what data is collected and where datasets are stored; (5) If you proceed, run the code in an isolated environment, limit tokens to least privilege, and monitor token usage/rotate tokens if anything looks unexpected. If the publisher cannot justify the missing manifest fields and the provenance of the skill, treat it as untrusted.

Type: OpenClaw Skill Name: social-listening-monitoring Version: 1.0.2 The skill provides a legitimate and well-documented template for building a brand reputation monitoring system. It uses Apify for web scraping, Claude for sentiment analysis, and Slack/Telegram for alerting, with all code logic in SKILL.md directly supporting these stated functions. No evidence of data exfiltration, malicious prompt injection, or unauthorized execution was found; the use of environment variables for API keys and standard libraries like axios and node-cron follows best practices for this type of application.