cargo-cli-analytics

To download workflow run results and segment exports from Cargo, use this Skill to query finished run payloads, batch node outputs, and full segment data. Commands return JSON format and support filters like --workflow-uuid and --batch-uuid for targeted data retrieval.

Yes, you can monitor workflow run metrics and count error rates per node. This Skill queries success and error counts, computes error rates, and scopes metrics to specific releases, batches, or date ranges using filters like --statuses and --created-after.

The best way to triage workflow failures is to count and retrieve only error runs using status filters, inspect batch summaries, and download the error payloads for investigation. This Skill supports filtering to isolate failed records for remediation and re-running.

Yes, exporting Cargo segment data and run metrics requires the @cargo-ai/cli installed and a valid Cargo API token with workspace access. This Skill relies on these prerequisites to execute commands and return JSON output for downstream analysis.

Cargo workflow run downloads may not return expected batch data if filters like --batch-uuid, --workflow-uuid, or --created-after are misconfigured. This Skill scopes queries precisely; verify your UUIDs and date ranges to ensure correct payload retrieval.

Yes, cargo-cli-analytics supports querying run metrics by date range. You can use the --created-after filter to scope per-node success and error counts to specific timeframes, enabling targeted monitoring and troubleshooting of recent workflow activity.