mxl-decompile

Decompile 1C MXL templates into a JSON DSL definition.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill mxl-decompile-mmmmmm786mngb-jpg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxl-decompile
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/mxl-decompile
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill mxl-decompile-mmmmmm786mngb-jpg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

Decompiles 1C MXL spreadsheet templates into a JSON DSL, enabling editing and reusing layout definitions in modern tooling.

Core Features & Use Cases

  • Decompile existing MXL templates into a portable JSON DSL.
  • Preserve fonts, borders, merges, named areas, and per-cell content for accurate editing.
  • Use in migration, analysis, and automation pipelines to tweak layouts and generate documentation.

Quick Start

Invoke the decompiler with a Template.xml to generate the JSON DSL output.

Frequently Asked Questions about mxl-decompile

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

FAQPage Schema
How do I convert a 1C MXL layout to JSON for editing?

To convert a 1C MXL layout to JSON, you decompile a Template.xml file into a JSON DSL definition. This transforms the spreadsheet template into a machine-readable format, preserving fonts, borders, merges, named areas, and cell data for accurate editing.

What is the best way to extract named areas and styles from 1C Template.xml?

Extracting named areas and styles from 1C Template.xml is done by decompiling the MXL template into a JSON DSL. This process preserves all fonts, borders, merges, and per-cell content, outputting a portable definition suitable for analysis and modification.

Can I use this MXL decompiler to migrate 1C sheet layouts to modern tooling?

Yes, you can use this MXL decompiler to migrate 1C sheet layouts to modern tooling. It converts Template.xml files into a portable JSON DSL, enabling the reuse and modification of layout definitions in automation pipelines and modern development environments.

Do I need lxml to parse 1C MXL templates into a JSON DSL?

Yes, you need lxml to parse 1C MXL templates into a JSON DSL. The decompiler relies on the lxml dependency to process the input Template.xml and successfully generate the JSON output containing areas, styles, and cell data.

Does the 1C MXL decompiler support outputting JSON to a file?

Yes, the 1C MXL decompiler supports outputting JSON to a file. When processing a Template.xml input, the tool can direct the resulting JSON DSL definition to standard output or write it directly to a file for later use.

Why does my 1C layout migration need a JSON DSL instead of raw XML?

A 1C layout migration needs a JSON DSL instead of raw XML because JSON provides a machine-readable format that is easier to edit and integrate into automation pipelines. Decompiling MXL templates to JSON simplifies tweaking layouts and generating documentation.