1c-mxl-decompile

Decompiles 1C spreadsheet document Template.xml files into a compact JSON DSL definition.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-mxl-decompile-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-mxl-decompile
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/1c-mxl/decompile
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-mxl-decompile-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Existing 1C spreadsheet layouts (MXL/Template.xml) are verbose XML files that are hard to read, analyze, or modify directly. This Skill converts them into a compact, human-readable JSON definition so you can inspect, edit, and regenerate print layouts programmatically. ## Core Features & Use Cases - XML to JSON DSL Conversion: Parses Template.xml and produces a structured JSON with columns, fonts, styles, areas, rows, and cells. - Automatic Naming: Generates meaningful font names (default, bold, header, small) and style names (bordered, bordered-center, bold-right) from format properties. - Smart Compression: Detects rowStyle patterns, compresses consecutive empty rows, merges column width ranges, and removes unused styles. - Use Case: You receive an existing print form layout from a 1C configuration. Decompile it to JSON, adjust areas or styles, then recompile with 1c-mxl-compile and verify with 1c-mxl-validate. ## Quick Start Ask the assistant to decompile the Template.xml of a 1C spreadsheet layout into JSON, providing the path to the template file.

Frequently Asked Questions about 1c-mxl-decompile

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

FAQPage Schema
How do I decompile a 1C MXL spreadsheet template to JSON?

Run the mxl-decompile.ps1 PowerShell script with the -TemplatePath parameter pointing to your Template.xml file. Optionally pass -OutputPath to write the JSON to a file; otherwise the JSON definition is printed to stdout.

What is the reverse operation of decompiling a 1C Template.xml?

The reverse operation is 1c-mxl-compile, which generates a Template.xml from the JSON DSL definition. The typical workflow is decompile to JSON, modify the JSON, recompile to XML, then validate with 1c-mxl-validate.

What does the JSON output of the MXL decompiler contain?

The JSON contains columns count, defaultWidth, optional columnWidths ranges, named fonts, named styles, and areas with rows. Rows include height, rowStyle, and cells with col, span, rowspan, style, param, template, or text values.

Does the decompiler handle merged cells and empty rows?

Yes. Merged cells are converted to span and rowspan attributes on the cell, and consecutive empty rows are compressed into a single { empty = N } entry. Uniformly formatted gap cells are detected as rowStyle.

What are the limitations of the 1C MXL decompiler?

It only processes named areas of type Rows and skips other named item types. It requires PowerShell and a valid Template.xml using the 1C v8 spreadsheet namespace; it does not read binary MXL files directly.