Preset CLI Skills

View saved version →

---
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)

Referenced files: 13

View saved version →

---
name: preset-cli-mutations
description: "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."
---

# preset-cli-mutations

Use for state-changing CLI operations: single-workspace writes (push, --force, --overwrite) and cross-workspace promotion (sync).

## Always

- Use `preset-cli` first to establish auth, workspace, and output context.
- CLI mutation surface only; route HTTP mutations to `preset-api-skills`.
- Preview before execution: native `--dry-run` for `sup sync run`, `sup user push`, and `sup user invite`; pull-and-diff for `sup chart push` / `sup dashboard push` / `sup dataset push` (no native `--dry-run`).
- Identify source AND target workspace explicitly before any cross-workspace operation.
- Require explicit typed user confirmation that contains the literal `--force` / `--overwrite` flag string when applicable.
- Redact tokens and credential-bearing output in transcripts.

## Decision Rules

- Distinguish single-workspace writes (`sup chart/dashboard/dataset push`) from cross-workspace sync (`sup sync run`).
- Treat `--force` and `--overwrite` as destructive flags; never invoke without explicit per-flag confirmation.
- For mutating command groups not named on this card, load command coverage and stop unless it explicitly marks the command as mutation-gated.
- Do not let CI / automation context bypass the confirmation step; refuse if no interactive operator is available.
- Route HTTP mutations to the API plugin; route MCP-driven workflows to the MCP plugin.

## Workflow Order

1. Resolve source and (if cross-workspace) target workspace.
2. Validate configuration where the command supports it (e.g. `sup sync validate`) before previewing.
3. Preview / diff to surface what will change.
4. Summarize asset counts, target effects, rollback expectations, and any destructive flags.
5. Ask for typed confirmation containing the literal destructive flag string.
6. Stop before execution and wait for the typed confirmation.
7. Execute only after confirmation.

## Retrieve

- Single-workspace writes (push, `--overwrite`, `--force`, dependency handling): [references/write-operations.md](references/write-operations.md)
- Cross-workspace promotion (sync, source/target, Jinja2, `--dry-run`): [references/cross-workspace-sync.md](references/cross-workspace-sync.md)
- Sync templating, rollback, and multi-target risk: [references/sync-templating-and-rollback.md](references/sync-templating-and-rollback.md)
- Preview and dry-run handling: [references/preview-and-dry-run.md](references/preview-and-dry-run.md)
- Confirmation template and abort triggers: [references/confirmation-template.md](references/confirmation-template.md)
- Confirmation overview and audit expectations: [references/confirmation-and-dry-run.md](references/confirmation-and-dry-run.md)
- Registered command coverage and uncovered mutation routing: load `preset-cli` and then `references/command-coverage.md`.
- Approval gates, redaction, abort triggers: load `preset-cli` and then `references/safety-policy.md`.

Referenced files: 6