For agents — source-of-truth: This skill is authored in roboflow/computer-vision-skills and shipped with the Roboflow plugin. If your client has loaded the plugin (you'll see roboflow:<name> skills in your available skills list), use those local skills — they're read fresh from disk every session. The same content served as MCP resources at roboflow://skills/<name>/... is a fallback for clients without the plugin and may lag this repo. Don't call ReadMcpResourceTool for roboflow://skills/... URIs when a local roboflow:<name> skill is available.

Batch Processing

Run a Roboflow Workflow over a very large set of images or videos on Roboflow's autoscaling compute. Every job processes a temporary Data Staging batch; the two input paths differ only in who fills that batch:

• Asset Library job — the files are already in Roboflow. You hand the platform a selection and it selects and stages them for you.
• Staged job — the files are outside Roboflow (local disk, cloud bucket, references file), so you stage them yourself with the inference-cli: only your machine and credentials can reach them. Nothing is imported into the workspace, and staged data expires after ~7 days.

Which path? Three questions