Claude Cursor GitHub Copilot Skill

preset-destructive-imports

Review destructive, overwrite-capable, sparse-update, all-assets restore, database import, and secret-bearing Preset import workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download preset-io-agent-skills-plugins_preset-api-skills_skills_preset-destructive-imports-73d2674.zip · 1 KB

preset-io/agent-skills 12 1 forks Apache-2.0 Updated 15d ago

Part of preset-io/agent-skills — 28 skills

Install

skills CLI

npx skills add https://github.com/preset-io/agent-skills/tree/master/plugins/preset-api-skills/skills/preset-destructive-imports

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install preset-io-agent-skills@llmmart

Git git clone https://github.com/preset-io/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole preset-io/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

preset-destructive-imports

Use for imports that can overwrite, replace, or materially change workspace assets.

Always

Auth and conventions come from preset-api (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. Consult preset-import-export for endpoint selection context when it is missing.
Treat overwrite and sparse-update imports as destructive.
Never print import secrets or database passwords.
Confirm destination workspace, bundle contents, overwrite behavior, secrets, expected changes, and rollback plan before live testing or import calls.

Decision Rules

Classify overwrite-capable, sparse-update, all-assets restore, database import, and secret-bearing import as destructive.
Require destructive approval wording before import.
Require backup or rollback plan.
Inspect bundle metadata without applying changes.

Workflow Order

Inspect bundle metadata.
Classify destructive impact.
Prepare backup, rollback, secret-handling, and approval summary.
Stop before import execution.

Retrieve

Destructive import review and approval checklist: references/destructive-import-approval.md
Approval policy: load preset-api and then references/safety-policy.md.

Files (agent-skills)

references

destructive-import-approval.md 1.6 KB

# Destructive Import Approval

Imports can create, overwrite, or replace dashboards, charts, datasets, databases, saved queries, themes, and all-assets bundles. Database imports can include passwords, SSH tunnel passwords, private keys, private key passwords, or encrypted extra secrets.

## Confirmation Required

Before running any import that uses `overwrite`, sparse update, all-assets restore behavior, database credentials, or replacement bundles, summarize:

1. Destination workspace hostname.
2. Import endpoint.
3. Bundle path and contained object types.
4. Object IDs, UUIDs, or names expected to be created or changed.
5. Whether `overwrite`, sparse update, passwords, or secret fields are provided.
6. Expected destructive effect.
7. Rollback or backup plan.

Wait for explicit confirmation.

Never print import secrets, database passwords, SSH tunnel passwords, private keys, private key passwords, or encrypted extra values in logs, examples, PR comments, or handoff notes.

## Endpoints

| Surface | Endpoint |
|---|---|
| All assets | `POST /api/v1/assets/import/` |
| Dashboards | `POST /api/v1/dashboard/import/` |
| Charts | `POST /api/v1/chart/import/` |
| Datasets | `POST /api/v1/dataset/import/` |
| Databases | `POST /api/v1/database/import/` |
| Saved queries | `POST /api/v1/saved_query/import/` |
| Themes | `POST /api/v1/theme/import/` |

## Validation Pattern

Prefer OpenAPI checks and bundle inspection before live import. Do not live-test imports on customer workspaces. Use a staging/dev workspace first, and only after the destination, overwrite behavior, and rollback plan are confirmed.

SKILL.md 1.6 KB

---
name: preset-destructive-imports
description: Review destructive, overwrite-capable, sparse-update, all-assets restore, database import, and secret-bearing Preset import workflows through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.
---

# preset-destructive-imports

Use for imports that can overwrite, replace, or materially change workspace assets.

## Always

- Auth and conventions come from `preset-api` (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. Consult `preset-import-export` for endpoint selection context when it is missing.
- Treat overwrite and sparse-update imports as destructive.
- Never print import secrets or database passwords.
- Confirm destination workspace, bundle contents, overwrite behavior, secrets, expected changes, and rollback plan before live testing or import calls.

## Decision Rules

- Classify overwrite-capable, sparse-update, all-assets restore, database import, and secret-bearing import as destructive.
- Require destructive approval wording before import.
- Require backup or rollback plan.
- Inspect bundle metadata without applying changes.

## Workflow Order

1. Inspect bundle metadata.
2. Classify destructive impact.
3. Prepare backup, rollback, secret-handling, and approval summary.
4. Stop before import execution.

## Retrieve

- Destructive import review and approval checklist: [references/destructive-import-approval.md](references/destructive-import-approval.md)
- Approval policy: load `preset-api` and then `references/safety-policy.md`.