webrobot-cli

Executes WebRobot CLI commands to manage projects, jobs, datasets, and pipeline manifests.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/WebRobot-Ltd/claude-code-webrobot-skills --skill webrobot-cli-webrobot-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webrobot-cli
Source: https://github.com/WebRobot-Ltd/claude-code-webrobot-skills/tree/main/skills/webrobot-cli
Command: npx skills add https://github.com/WebRobot-Ltd/claude-code-webrobot-skills --skill webrobot-cli-webrobot-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing the WebRobot data platform through shell commands requires knowing dozens of command groups, flags, and auth configuration details. This Skill translates natural-language tasks into correct webrobot CLI invocations, handling pipelines, jobs, datasets, plugins, and credentials without memorizing the command surface. ## Core Features & Use Cases - Pipeline deployment and execution: Validate, apply, and run pipeline YAML manifests with webrobot pipeline run -f x.yaml --follow, streaming logs and returning script-friendly exit codes. - Resource management: List, create, and inspect projects, jobs, agents, datasets, cloud credentials, and LLM providers via the CLI's command groups. - Plugin and extension management: Install partner CLI plugin JARs, scaffold new plugin source trees, and register Python extensions on agents. - Use Case: A data engineer asks to deploy a scraping pipeline and monitor it. The Skill runs webrobot pipeline run -f my-pipeline.yaml --follow, streams the job logs, and reports success or failure based on the exit code. ## Quick Start Ask the assistant to list your WebRobot projects or run a pipeline manifest file using the webrobot CLI.

Frequently Asked Questions about webrobot-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a WebRobot pipeline from the command line?

Run `webrobot pipeline run -f my-pipeline.yaml --follow` to validate, register, and execute the manifest in one step. It streams job logs to the terminal and returns exit code 0 on COMPLETED, non-zero on failure.

When should I use the WebRobot CLI versus the MCP tools?

Use MCP tools for conversational ad-hoc queries returning structured JSON. Use the CLI for batch shell scripts, pipeline manifest deployment with log streaming, plugin JAR installation, and anything needing local shell context like environment variables.

How do I authenticate the WebRobot CLI?

Run `webrobot config init` to create ~/.webrobot/config.cfg with your api_endpoint and apikey or JWT. Verify authentication with `webrobot auth me`, which returns your resolved org_id and user_id.

How do I install a WebRobot CLI plugin JAR?

Use `webrobot cli plugins install` with Maven coordinates, a local JAR path, or a direct URL. Installed plugins register new subcommands and are stored in ~/.webrobot/plugins/; list them with `webrobot cli plugins list`.

Why do WebRobot CLI commands return 401 errors?

A 401 means missing or expired credentials in ~/.webrobot/config.cfg. Run `webrobot auth me` to check the current auth state, then re-run `webrobot config init` or update the apikey or jwt value.

Can I script WebRobot CLI output with jq?

Yes, most commands accept `--output json` alongside table and yaml formats. Pipe the JSON output to jq for loops over projects, status polling until a job reaches COMPLETED, or extracting resource IDs in shell scripts.