What problem does it solve? Running Argos visual-testing commands from a shell or CI pipeline fails silently when the wrong token type is used or when build references, change IDs, and project flags are mixed up. This Skill encodes the Argos CLI's token model, output contract, and full command map so agents and developers run commands correctly the first time. ## Core Features & Use Cases - Token model guidance: Distinguishes project tokens, personal access tokens (PAT), and CI tokens, with the exact resolution order (--token, ARGOS_TOKEN, argos login) per command group. - Full command map: Covers build inspection, snapshot diffs, reviews and reviewers, comments, test flakiness analysis, change ignore/unignore, project and team administration, automation rules, analytics, media management, and CI upload/finalize flows. - Output contract for agents: Mandates --json for parsing, documents the stderr error format and exit codes, and prohibits printing token values. - Use Case: A CI build shows unexpected visual diffs. Use this Skill to fetch build snapshots --needs-review --json with a project token, inspect each diff's change.id and flakiness metrics, then approve the build or ignore a recurring flaky change with a PAT. ## Quick Start Use the argos-cli skill to list the snapshots needing review on the latest Argos build and approve it if the diffs look intentional.
