Preny Analytics

Kết nối trực tiếp với Preny AI Chatbot để tự động tổng hợp và phân tích dữ liệu bán hàng theo thời gian thực.

Do not install or run this skill until the author clarifies which credentials are required and why multiple env variables are referenced. Specific actions to take before proceeding: - Ask the author/maintainer why some scripts require PRENY_API_KEY and PRENY_WORKSPACE_ID while SKILL.md declares only PRENY_TOKEN. If PRENY_TOKEN alone should work, request updated scripts that use it consistently. - Inspect and run the scripts locally in a safe environment (not on production hosts) before granting any tokens. The scripts will make API calls to Preny domains; verify those domains with Preny support if unsure. - Avoid pasting your Preny token into third-party sites. Follow the README's local steps to obtain a token, but treat the token as sensitive (it grants access to business data). Rotate the token if you accidentally disclose it. - Prefer an official Preny integration or documentation from pren y.ai if available. If you must use this skill, limit the account/workspace scope of the token and consider creating a dedicated workspace or read-only credentials (if supported) rather than using a full-access token. Because of the mismatch across files and undocumented additional env requirements, treat this package as untrusted until clarified.

Type: OpenClaw Skill Name: preny-analytics Version: 1.5.0 The preny-analytics skill bundle provides a suite of Bash and Node.js scripts designed to interface with the Preny AI Chatbot API for sales data visualization and conversation management. The scripts (scripts/preny-stats.sh, scripts/preny-handler.js, etc.) use a user-provided PRENY_TOKEN to fetch metrics such as customer counts, message volume, and conversion rates from legitimate endpoints (api.preny.ai and api-production.prenychatbot.ai). While the documentation (docs/how-to-get-token.md) instructs users on how to manually extract session tokens from their browser, this is presented transparently as a requirement for the integration to function. The code logic is straightforward, lacks obfuscation, and contains no evidence of data exfiltration to unauthorized third parties or malicious command execution.