From redash-cli
Help someone use the installed redash CLI. Use this for configuring profiles, checking authentication, listing data sources or dashboards, checking admin query queue status, inviting users, running SQL, exporting JSON or CSV, explaining PostgreSQL query plans, and choosing safe command examples.
How this skill is triggered — by the user, by Claude, or both
Slash command
/redash-cli:redash-cli-usageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill after the CLI is installed and the user wants help running `redash` commands.
Use this skill after the CLI is installed and the user wants help running redash commands.
Do not use it for repository implementation or release changes; use redash-cli-dev instead. Do not use it for fresh machine or checkout setup; use redash-cli-setup instead.
redash command, not modify the repository.redash config set.--profile when the user mentions multiple environments.Create or update a profile:
redash config set --profile default --url https://redash.example.com
List profiles:
redash config list
Set the default profile:
redash config use default
Test authentication:
redash auth test
Use a specific profile:
redash auth test --profile staging
Notes:
~/.config/redash-cli/config.json.redash-cli service.List data sources before running queries:
redash data-sources list
List dashboards:
redash dashboards list
Use paging and sort order when the user needs more control:
redash dashboards list --page 1 --page-size 20 --order=-created_at
Get a dashboard by slug:
redash dashboards get sales-overview
Warn that dashboard slugs can change when dashboards are renamed in Redash.
Show Redash query queue and worker status:
redash admin queue-status
Use a non-default profile:
redash admin queue-status --profile staging
Guidance:
admin queue-status fetches the Redash admin query queue status and prints JSON.Before running user-provided SQL:
LIMIT, SELECT *, and aggregation over unknown ranges as potentially heavy.redash query explain before suggesting redash query run.query explain is unavailable for the data source, ask the user to confirm the query cost risk before running it and suggest adding restrictive filters, a date range, and LIMIT.SELECT or WITH queries.Run SQL and return JSON:
redash query run --data-source-id 1 --sql "select 1 as value"
Run SQL and return CSV:
redash query run --data-source-id 1 --sql "select 1 as value" --format csv
Use a non-default profile:
redash query run --profile staging --data-source-id 1 --sql "select current_date"
Guidance:
--format csv when the user wants spreadsheet-friendly output.LIMIT to exploratory queries.Preview a PostgreSQL query plan without running the query:
redash query explain --data-source-id 1 --sql "select * from invoices"
Explain the constraints:
query explain supports PostgreSQL data sources only.EXPLAIN (FORMAT JSON) without ANALYZE.SELECT or WITH query.Invite a user:
redash users invite --name "Taro Yamada" --email [email protected]
Create a pending invitation without sending email:
redash users invite --name "Taro Yamada" --email [email protected] --no-send-email
Warn that user invitation requires an admin API key.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub urugus/redash-cli --plugin redash-cli