AI Search Rank Tracker

This skill implements an LLM-based visibility tracker and legitimately needs API keys for the engines it queries (OpenAI, Anthropic, possibly routing proxies). That is proportionate to its purpose, but the registry metadata incorrectly lists no required environment variables — so the install will create/expect a .env file containing your API keys. Before installing: 1) Inspect the .env.example to see what keys are required and do not use high-privilege or shared production credentials; create a dedicated/limited key if possible. 2) Review src/* files (index.js, engines.js, parser.js) yourself to confirm which endpoints are called and whether any external URLs are used beyond vendor SDKs. 3) Run npm install and the script in an isolated environment (or container) if you have any doubt. 4) Because the installer copies .env.example to .env, it will not overwrite an existing .env; still verify contents before running. If the publisher updates the registry metadata to explicitly list the required env vars (OPENAI_API_KEY, ANTHROPIC_API_KEY, or any router keys) and documents exactly which services are contacted, my assessment would move closer to benign; as-is the missing metadata is a transparency concern.