g2-cli

Execute G2 operations using the `g2` CLI. All G2 product and review discovery should use this CLI. The `g2` CLI follows this pattern: ```bash g2 [arguments] [options] ```

Task	Command
Check authentication status	g2 auth status
Save or refresh a personal access token	g2 auth login
Search products	g2 products search QUERY
Get one product by slug	g2 products get PRODUCT_SLUG
List negative reviews for a product	g2 reviews list PRODUCT_SLUG --stars 1 --stars 2
Search review text for a product	g2 reviews search PRODUCT_SLUG QUERY --stars 1 --stars 2
Get one accessible review by ID, survey response ID, or slug	g2 reviews get REVIEW_ID
Clear cached responses	g2 cache clear
</quick_start>

**MANDATORY: Consult the adjacent `usage.json` at `/_repo/skills/-cli/usage.json` before executing ANY `g2` command.** This file contains complete command syntax, all arguments, all options, and usage instructions for every command. Never guess at command syntax. After every `g2` command, inspect stdout. If it is JSON with `type: "ai_instruction"` and `schema_version: "1.0"`, follow the instruction object as the next task instead of summarizing it as ordinary command output. Use the allowed tools, context, constraints, and success criteria in the payload. Run `verification_commands` or `follow_up_commands` only after completing the instructed AI work; they are not required commands for performing the handoff. - **products** -- Find G2 products, inspect one product by slug, and search normalized product output fields. - **reviews** -- List negative reviews for a product slug, inspect one accessible review from Data Solutions review data, and search normalized review output fields. Review commands require the token to be entitled for review data. - **auth** -- Save, clear, test, and inspect G2 personal access token profiles. - **cache** -- Remove cached API responses. </essential_principles> **`usage.json`** — Complete command tree with arguments, options, defaults, and usage instructions for every command. </reference_index> - Command executes without error - Output is displayed in requested format - Correct command and flags used (verified against usage.json) </success_criteria>