Operator

Manage your Operator fleet of AI agent instances. Create, configure, monitor, message, and manage OpenClaw agents. Handles authentication, instance lifecycle...

This skill appears to be what it says: a thin set of instructions to talk to an Operator service and store an Operator API key in ~/.operator/config.json. Before installing or using it, verify that you actually trust the operator.io domain and the service owner (there's no homepage or source listed). Be aware that the flow will create a plaintext JSON file with your API key in your home directory — set its permissions (chmod 600 ~/.operator/config.json) and treat the key like any secret. Confirm the API key scopes/privileges on the Operator side and rotate the key if you later suspect compromise. If you need higher assurance, ask the publisher for source code or an official homepage and verify the owner identity; without that provenance you are trusting the remote Operator service and whoever controls the operator.io domain.

Type: OpenClaw Skill Name: operator Version: 1.0.0 The 'operator' skill is a legitimate integration for managing AI agent fleets via the operator.io platform. It implements standard CLI-style authentication by polling a session endpoint, stores credentials locally in ~/.operator/config.json, and interacts with a central API to manage instances and secrets. The use of python3 and curl for parsing SSE streams is consistent with the stated purpose and lacks indicators of malicious intent or unauthorized data exfiltration.