Manage stripe-q via CLI - {{RESOURCES_LIST}}. Use when user mentions 'stripe-q' or wants to interact with the stripe-q API.
Use the stripe-q-cli skill when you need to:
{{WHEN_TO_USE_HELP}}
Document the actual capabilities of stripe-q-cli after inspecting the generated commands.
Prefer task-oriented bullets over endpoint names.
{{CAPABILITIES_HELP}}
Add concrete, domain-specific requests an agent could solve with this CLI. Keep them short and action-oriented.
{{USE_CASES_HELP}}
If stripe-q-cli is not found, install and build it:
bun --version || curl -fsSL https://bun.sh/install | bash
npx api2cli bundle stripe-q
npx api2cli link stripe-q
api2cli link adds ~/.local/bin to PATH automatically. The CLI is available in the next command.
Always use --json flag when calling commands programmatically.
--json for agent-driven calls so downstream steps can parse the result.--help if the exact action or flags are unclear instead of guessing.stripe-q-cli auth set "your-token"
stripe-q-cli auth test
Auth commands: auth set <token>, auth show, auth remove, auth test
Token is stored in ~/.config/tokens/stripe-q-cli.txt.
{{RESOURCES_HELP}}
--json returns a standardized envelope:
{ "ok": true, "data": { ... }, "meta": { "total": 42 } }
On error: { "ok": false, "error": { "message": "...", "status": 401 } }
stripe-q-cli --help # List all resources and global flags
stripe-q-cli <resource> --help # List all actions for a resource
stripe-q-cli <resource> <action> --help # Show flags for a specific action
All commands support: --json, --format <text|json|csv|yaml>, --verbose, --no-color, --no-header
Exit codes: 0 = success, 1 = API error, 2 = usage error