convert-xml

Convert FileMaker SaXML exports into a structured DuckDB catalog.

17|5|Updated Apr 28, 2026

Search Tags:#automation #database #analysis #xml #duckdb #filemaker

Ready to run

npx skills add https://github.com/marcel-more/fm-lab --skill convert-xml

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convert-xml
Source: https://github.com/marcel-more/fm-lab/tree/main/.claude/skills/convert-xml
Command: npx skills add https://github.com/marcel-more/fm-lab --skill convert-xml

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the lack of native programmatic access to FileMaker solution structures by converting proprietary SaXML exports into a high-performance, queryable DuckDB database.

Core Features & Use Cases

Automated Conversion: Handles UTF-16 to UTF-8 encoding and parses complex XML structures into relational tables.
Deep Analysis: Enables cross-reference analysis of scripts, fields, layouts, and relationships using SQL.
Use Case: A developer needs to audit all dependencies for a specific field across a large FileMaker solution; this skill builds the catalog required to run that analysis in seconds.

Quick Start

Use the convert-xml skill to import all FileMaker XML files from the current solution inbox into the database.

Frequently Asked Questions about convert-xml

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert FileMaker SaXML exports into a queryable database?▼

To convert FileMaker SaXML exports into a queryable database, this skill parses complex XML structures and loads them into a high-performance DuckDB catalog. It handles UTF-16 to UTF-8 encoding automatically, enabling deep cross-reference analysis of scripts, fields, and layouts using SQL.

Can I audit field dependencies across a large FileMaker solution using SQL?▼

You can audit field dependencies across a large FileMaker solution using SQL by transforming the SaXML exports into a structured DuckDB catalog. Once imported, this enables rapid cross-reference analysis of scripts, fields, layouts, and relationships in seconds.

Do I need a local DuckDB environment to process FileMaker XML bundles?▼

Yes, you need a local DuckDB environment to process FileMaker XML bundles. The conversion requires access to the solution XML inbox directory to perform batch processing of solution bundles with automated schema versioning and dependency mapping.

What's the best way to analyze FileMaker relationships and scripts in bulk?▼

The best way to analyze FileMaker relationships and scripts in bulk is converting proprietary SaXML exports into a relational DuckDB database. This approach supports batch processing of solution bundles and allows automated schema versioning for comprehensive cross-reference analysis.

Does this conversion process handle UTF-16 encoded FileMaker XML files?▼

Yes, the conversion process handles UTF-16 encoded FileMaker XML files by automatically transforming them to UTF-8 encoding. This ensures complex XML structures are parsed correctly into relational tables within the DuckDB catalog for downstream analysis.