2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill robotx- _meta.json280 B
- SKILL.md3.2 KB
Overview
This skill provides CLI-driven deployment, version management, and status checking for RobotX applications using the robotx CLI. It streamlines creating or updating projects, listing versions, fetching logs, and publishing builds with machine-readable JSON output. The skill is designed for interactive use and CI automation, with guidance for authentication and structured outputs.
How this skill works
The skill wraps the robotx CLI commands to perform deploy, projects, versions, status, logs, and publish operations. It verifies local authentication first, supports environment variables or a ~/.robotx.yaml config, and recommends JSON output for agent workflows. Progress and human logs go to stderr while structured results are returned on stdout as JSON.
When to use it
- Deploy a new RobotX application or update an existing one using deploy --name
- List projects or versions to discover available deployments and builds
- Check build or project status and tail logs for debugging or CI validation
- Publish a specific build to make it available to users
- Integrate RobotX operations into automation pipelines or agent workflows
Best practices
- Always verify authentication before running commands (robotx projects --limit 1 --output json)
- Prefer environment variables in CI: ROBOTX_BASE_URL and ROBOTX_API_KEY
- Use --output json for machine-readable results; treat stdout as JSON and stderr as progress/logs
- Use deploy --name for create-or-update behavior within the same owner
- Require --build-id when requesting logs via status --logs to avoid ambiguous queries
Example use cases
- CI pipeline: build artifact, robotx deploy . --name my-app --wait=true --output json, then robotx publish to release
- Interactive debugging: robotx status --project-id proj_123 --build-id build_456 --output json and robotx logs --build-id build_456
- Inventory: list all projects and versions programmatically with robotx projects --limit 50 --output json and robotx versions --project-id proj_123
- Non-interactive auth: set ROBOTX_BASE_URL and ROBOTX_API_KEY in CI secrets and run robotx commands without device login
FAQ
Export ROBOTX_BASE_URL and ROBOTX_API_KEY as environment variables or write them to ~/.robotx.yaml in the CI user. This avoids device login prompts.
What output format should agents expect?
Request --output json on all commands. JSON is written to stdout while progress and human-friendly logs go to stderr, so parse stdout for structured data.