LLM Signal GEO Analyst

This package appears to do what it says: call your LLM Signal endpoints and return action plans. Before installing, consider the following: (1) the scripts embed your API key in the JSON payload and in the curl command — that means the key (and any persisted run history) may be stored on the remote service and the key could be exposed in local process lists or shell history. Prefer sending only an authentication header and avoid including the key in request bodies if the service accepts header auth. (2) Avoid running these scripts on multi-tenant/shared hosts where process args are visible, or use safer calling patterns (e.g., pass JSON on stdin or use .netrc/token files) to avoid command-line leakage. (3) Confirm what 'persist=true' stores on the vendor side; if it stores full payloads, do not include secrets in those payloads. (4) Use a least-privilege/rotatable API key for LLMSIGNAL, and rotate it if you decide to remove the skill. These are operational hygiene items — the skill's requested resources are otherwise consistent with its stated purpose.