Oc Call

通过 OpenClaw Gateway HTTP API 调用远程 OpenClaw 实例，支持多轮会话保持。 当用户说"用 oc 回答"、"用 openclaw 回答"、"oc 回答"、或发送 /oc 命令时触发。 用于调用内网另一台机器（192.168.123.106）上的 OpenClaw 进行问答，保持会...

This skill implements exactly what it says — it will POST user queries to an OpenClaw Gateway on the internal IP 192.168.123.106 and persist a session key in ~/.oc_session — but it contains hard-coded URL and token values and its documentation claims environment-variable overrides that the code does not actually use. Before installing or running: (1) review and, if needed, remove or replace the hard-coded OC_TOKEN and OC_URL in scripts/oc_call.py; (2) if you expect to supply credentials via environment variables, update the script so it actually reads them (or ensure they are removed from the repo); (3) consider whether calling an internal IP from an agent is acceptable in your environment; (4) be aware the skill writes ~/.oc_session (protect that file or change its path); (5) if you do not trust the embedded token/IP, do not install or run the skill. If the author can provide a corrected version that reads OC_URL and OC_TOKEN from env vars (and removes hard-coded secrets), the concerns here would be largely resolved.