preset-cli
/preset-cli
Drive Preset's `sup` CLI (PyPI package `superset-sup`) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths.
- Author
- preset-io ↗
- Repository
- agent-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 09.10.2026
Assessment and security
- Files in this package
- 14
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Drive Preset's `sup` CLI (PyPI package `superset-sup`) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths.
Original author description
Drive Preset's `sup` CLI (PyPI package `superset-sup`) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths.
How it works
- Always
- Decision Rules
- Workflow Order
- Retrieve
SKILL.md preview
--- name: preset-cli description: Drive Preset's `sup` CLI (PyPI package `superset-sup`) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths. --- # preset-cli Use as the foundation for shell, scripting, CI/CD, and agent-driven Preset workflows through the `sup` CLI. ## Always - CLI surface only; stay on MCP or direct API if that's what the user requested. - Default to `--json` for automation and agent consumption. - Keep `SUP_PRESET_API_TOKEN` / `SUP_PRESET_API_SECRET` out of command lines and shared output; use env vars or `sup config auth`, never paste secrets on the command line. - Route push, sync, overwrite, and `--force` to `preset-cli-mutations`. - Redact tokens and credential-bearing output in transcripts. ## Decision Rules - Classify CLI vs MCP vs direct API intent before acting; if MCP or direct API was requested, defer to that plugin. - Run metadata reads and explicitly requested data-returning reads (e.g. `sup sql`, `sup chart data`) on familiar workspaces directly with bounded output; for `sup sql`, this direct path requires a pure single-statement `SELECT`. Load safety policy before mutations, SQL that is not a pure single-statement `SELECT`, untrusted-source SQL, unfamiliar workspaces, or broad outputs. - Choose output format based on the downstream consumer: `--json` for automation, `--csv` for files, default Rich for humans, `--porcelain` for shell pipelines. - If a command group is not named on this card, load command coverage before composing commands. - For mutating intent, stop and load `preset-cli-mutations` rather than continuing on this card. Non-`SELECT` SQL is confirmation-gated by the safety policy even when it is pasted by the user for a familiar workspace. ## Workflow Order 1. Establish install, auth, and workspace context. 2. Choose output format. 3. Classify risk (metadata read vs data-returning read vs mutation). 4. Load the focused reference for the operation. 5. Run only the safe / read command. 6. Redact output before sharing. ## Retrieve - Install, entry points, OAuth, env vars: [references/install-and-auth.md](references/install-and-auth.md) - Config precedence and source resolution: [references/config-precedence.md](references/config-precedence.md) - Workspace selection and `--workspace-id` override: [references/workspace-and-config.md](references/workspace-and-config.md) - Registered command coverage and routing: [references/command-coverage.md](references/command-coverage.md) - Output formats and exit behavior: [references/output-formats.md](references/output-formats.md) - Asset read/export entity scope: [references/assets-read.md](references/assets-read.md) - Asset list filter matrix: [references/asset-filter-matrix.md](references/asset-filter-matrix.md) - Ad-hoc SQL routing: [references/sql-and-query.md](references/sql-and-query.md) - SQL/data-returning read safety: [references/sql-data-safety.md](references/sql-data-safety.md) - Saved query reads: [references/saved-query-reads.md](references/saved-query-reads.md) - Detailed command examples: [references/command-examples.md](references/command-examples.md) - CLI vs API routing decision: [references/cli-vs-api.md](references/cli-vs-api.md) - Approval gates and credential redaction: [references/safety-policy.md](references/safety-policy.md)
Files in this package (14)
- SKILL.md 3 KB
- references/asset-filter-matrix.md 1 KB
- references/assets-read.md 2 KB
- references/cli-vs-api.md 3 KB
- references/command-coverage.md 5 KB
- references/command-examples.md 1 KB
- references/config-precedence.md 2 KB
- references/install-and-auth.md 3 KB
- references/output-formats.md 3 KB
- references/safety-policy.md 5 KB
- references/saved-query-reads.md 1 KB
- references/sql-and-query.md 2 KB
- references/sql-data-safety.md 2 KB
- references/workspace-and-config.md 4 KB
Versions
The database has no other skills named preset-cli.
Database snapshot: 13.11.2026 · package version 19095b00c4f6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90preset-cli-mutations
State-changing Preset `sup` CLI workflows: chart/dashboard/dataset push, user push/invite, destructive flags, and cross-workspace sync. Use only for CLI mutation workflows. Do not use for MCP-only work. Do not use for direct HTTP/SDK mutations. - 90preset-database-connections
Inspect or route Preset database connection configuration, validation, OAuth, upload, create, update, and delete workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work. - 95sup-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code - 100sup
Catch the user up in one screen — what got done, what changed, what waits on them, what comes next. Use when the user asks "sup", "what's up", "where are we", "catch me up" or "status report", returns after a break, or a long stretch of work ends. - 90superset-and-metrics-serving
Guides agents through Superset and metrics-serving workflows. Use when publishing governed metrics to Superset, defining semantic consistency for dashboards, or managing chart-ready analytical datasets. - 85sup-410-issue-a-refund-or-credit
Work out the refund or credit a customer is owed under the written policy, issue it once after the SUP 450 checks pass, confirm it, and tell the customer exactly what happens next. Use when a refund or store credit is due.