Preny Analytics

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.

These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.