How do I install the Import Export skill?

Run npx skillmds@latest add ahs12/import-export in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Import Export safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Import Export?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Import Export free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Import Export?

ahs12 (@ahs12) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Import Export by ahs12 — Agent Skill

Name: Import Export
Author: ahs12

File contents

Import and Export

Read First

src/components/ImportDialog.tsx and src/components/ExportDialog.tsx for UI dispatch.
src/lib/importer.ts and src/lib/importer/ for parser contracts.
src/workers/sqlite-ddl.worker.ts for SQLite worker boundaries.
src/lib/exporter/, src/lib/mermaid.ts, and src/lib/types.ts for output and model semantics.

Change Rules

Select the parser from the declared database dialect and keep progress/diagnostic behavior intact.
Preserve table and column IDs, positions, colors, locks, notes, zones, viewport, and relationship metadata when the format supports them.
Treat custom SQL parsers as dialect-specific state machines. Do not assume MySQL, PostgreSQL, and SQLite syntax coverage is interchangeable.
Keep SQLite parsing in the worker and handle worker errors without leaving a half-imported diagram.
JSON imports require safe validation before entering the store. Never trust arbitrary node, edge, or date data merely because the top-level arrays exist.
DBML save synchronization uses heuristic matching; test similarly named and structurally similar tables, IDs, positions, and repeated save cycles.
Generated SQL, DBML, Mermaid, SVG, and migrations are output artifacts. Review quoting, composite keys, comments, notes/zones, and unsupported features explicitly.

Verification Matrix

Import valid and invalid MySQL, PostgreSQL, SQLite, DBML, and application JSON.
Export and re-import each supported round-trip format where applicable.
Include composite relationships, indexes, comments, nullable/default/generated columns, notes, zones, and locked diagrams when relevant.
Confirm diagnostics are visible and failures do not mutate the active diagram.

---name: import-exportdescription: Change SQL, SQLite worker, DBML, JSON, Mermaid, SVG, or database export/import flows while preserving diagram semantics and round trips. Use when adding dialect support or changing parser/exporter behavior.---# Import and Export## Read First- `src/components/ImportDialog.tsx` and `src/components/ExportDialog.tsx` for UI dispatch.- `src/lib/importer.ts` and `src/lib/importer/` for parser contracts.- `src/workers/sqlite-ddl.worker.ts` for SQLite worker boundaries.- `src/lib/exporter/`, `src/lib/mermaid.ts`, and `src/lib/types.ts` for output and model semantics.## Change Rules1. Select the parser from the declared database dialect and keep progress/diagnostic behavior intact.2. Preserve table and column IDs, positions, colors, locks, notes, zones, viewport, and relationship metadata when the format supports them.3. Treat custom SQL parsers as dialect-specific state machines. Do not assume MySQL, PostgreSQL, and SQLite syntax coverage is interchangeable.4. Keep SQLite parsing in the worker and handle worker errors without leaving a half-imported diagram.5. JSON imports require safe validation before entering the store. Never trust arbitrary node, edge, or date data merely because the top-level arrays exist.6. DBML save synchronization uses heuristic matching; test similarly named and structurally similar tables, IDs, positions, and repeated save cycles.7. Generated SQL, DBML, Mermaid, SVG, and migrations are output artifacts. Review quoting, composite keys, comments, notes/zones, and unsupported features explicitly.## Verification Matrix- Import valid and invalid MySQL, PostgreSQL, SQLite, DBML, and application JSON.- Export and re-import each supported round-trip format where applicable.- Include composite relationships, indexes, comments, nullable/default/generated columns, notes, zones, and locked diagrams when relevant.- Confirm diagnostics are visible and failures do not mutate the active diagram.

Frequently asked questions

Import Export