preset-admin
Manage Preset teams, workspaces, memberships, invites, role identifiers, seat checks, and audit logs through direct Management…
@preset-ioInstall SkillDevelopment
Skill
/preset-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.
Claude Code
$ npx -y skills add preset-io/agent-skills --skill preset-cli-mutations --agent claude-code
Codex
$ npx skills add preset-io/agent-skills --skill preset-cli-mutations -a codex -y
Cursor
$ npx skills add preset-io/agent-skills --skill preset-cli-mutations -a cursor -y
Gemini CLI
$ npx skills add preset-io/agent-skills --skill preset-cli-mutations -a gemini-cli -y
GitHub Copilot
$ npx skills add preset-io/agent-skills --skill preset-cli-mutations -a github-copilot -y
OpenCode
$ npx skills add preset-io/agent-skills --skill preset-cli-mutations -a opencode -y
Windsurf
$ npx skills add preset-io/agent-skills --skill preset-cli-mutations -a windsurf -y
SKILL.md
preset-cli-mutations.SKILL.mdname: 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`.
Read more
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`.
Ships withagent-skills
Agent guidance for working with Preset, Apache Superset, and Superset MCP tools. The skills are authored once and load across every supported agent client — see Supported clients.
1329 skills
Stars on GitHub
Momentum
- stars in total
- 13
Other skills on agent-skills.
@preset-ioInstall Skillpreset-api
Prepare direct Preset API access: auth, JWT exchange, base URLs, pagination, Rison parameters, response handling, and shared API…
@preset-ioInstall Skillpreset-dashboards
Inspect Preset workspace dashboards, charts, dashboard composition, screenshots, thumbnails, chart data, and chart/dashboard…
@preset-ioInstall Skillpreset-database-connec…
Inspect or route Preset database connection configuration, validation, OAuth, upload, create, update, and delete workflows…
@preset-ioInstall Skillpreset-datasets
Inspect Preset workspace datasets, database metadata, schemas, tables, columns, metrics, and dataset/database workflow routing…
@preset-ioInstall Skillpreset-destructive-imp…
Review destructive, overwrite-capable, sparse-update, all-assets restore, database import, and secret-bearing Preset import…
@preset-ioInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about preset-cli-mutations.
- Which coding agents can use preset-cli-mutations?
- preset-cli-mutations installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.