Toggle

This skill appears coherent for its stated purpose, but consider the following before installing: - Endpoint trust: the script sends your TOGGLE_API_KEY to https://ai-x.toggle.pro. Only use a key if you trust that service. Verify the domain and integration page before adding a real API key. - Least privilege: create a dedicated ToggleX integration key with limited scope/expiry if possible, rather than using a broad or long-lived user key. - Memory persistence: when you run with --persist (or use the suggested ../../memory path), the skill will write markdown files containing your activity data. Confirm where those files will be stored and who/what can read them. - Cron checks: the script reads ~/.openclaw/cron/jobs.json to check scheduling. It will create state.yaml inside the skill dir if missing. Review that file before trusting automated runs. - Downstream automation caution: SKILL.md encourages proactive nudges and automations. The script returns raw JSON that can include domain strings (the sample even shows local addresses). The skill itself does not fetch or act on those domains, but if you enable agent-driven automations, ensure you limit any automatic following of URLs (to avoid accidental access to internal services or SSRF-like risks). - Operational safety: do not paste the API key into chat; set it via your OpenClaw config or environment as documented. If you have doubts after running the skill, revoke the key on the provider side. If you trust ai-x.toggle.pro and are comfortable with the skill writing memory files and reading your OpenClaw cron config, the skill is consistent and reasonable to install.