robotx

What This Skill Does

The robotx skill provides a seamless interface for interacting with the RobotX platform directly from your agentic workflow. It acts as a wrapper around the robotx CLI, enabling automated deployment, project management, version tracking, and status monitoring. Designed for developers and DevOps engineers, this tool allows agents to trigger builds, inspect logs, and publish new versions without requiring manual CLI access or shell context switching.

Installation

To install this skill, use the command: clawhub install openclaw/skills/skills/haibingtown/robotx. Ensure the environment has internet access to execute the installation scripts. For binary-first deployment, the skill utilizes a standard shell script that pulls from the official repository, avoiding the need for Go language dependencies. If a source-based install is preferred, the skill supports direct go install commands.

Use Cases

• Automated CI/CD pipelines: Agents can watch a repository and automatically call robotx deploy upon receiving a pull request notification.
• Error handling and monitoring: When a deployment fails, the agent can autonomously query robotx logs to identify the cause of failure and report back to the user.
• Version Lifecycle Management: Automate the promotion of builds to production using the robotx publish command after verifying status checks.
• Audit and Compliance: List all active projects and their associated versions to maintain an inventory of running applications.

Example Prompts

1. "Check the current status of the production project with ID proj_789 and print the latest logs if the build is failed."
2. "Deploy the current directory as a new project named 'customer-dashboard' and publish it immediately after success."
3. "List my last 10 RobotX projects and tell me which ones have not had a build in the last week."

Tips & Limitations

• Always pipe outputs to --output json to ensure your agent can reliably parse the response for downstream reasoning.
• Ensure environment variables ROBOTX_BASE_URL and ROBOTX_API_KEY are securely managed in your agent's secret store. Do not hardcode credentials in prompts.
• When running in non-interactive CI environments, avoid robotx login and prefer using environment variables for authentication to prevent hanging processes.
• The CLI writes progress logs to stderr, which the agent should handle as metadata rather than primary data, focusing on the structured stdout for final results.