1c-mxl-validate

Validates structural correctness of 1C spreadsheet document Template.xml files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? 1C spreadsheet layouts (MXL/Template.xml) can contain structural errors—invalid palette indices, out-of-range row or column references, broken merge ranges—that the 1C platform silently ignores, causing data loss or layout corruption. This Skill detects those errors before they reach production. ## Core Features & Use Cases - Structural Validation: Runs 12 checks covering height consistency, format/font/border palette indices, column set references, named area bounds, merge ranges, and picture indices. - Flexible Targeting: Accepts either a direct path to Template.xml or a processor/template name pair resolved against the source directory. - Overflow Protection: Stops after a configurable number of errors (default 20) and always prints an error/warning summary with a meaningful exit code. - Use Case: After generating or editing a print form layout for a 1C data processor, run the validator to catch a cell format index exceeding the format palette before building the configuration. ## Quick Start Ask the assistant to validate the Template.xml layout of your 1C processor by running the mxl-validate PowerShell script with the template path or processor and template names.

Frequently Asked Questions about 1c-mxl-validate

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

FAQPage Schema
How do I validate a 1C MXL Template.xml file?

Run the mxl-validate.ps1 PowerShell script with the -TemplatePath parameter pointing to your Template.xml file. Alternatively, pass -ProcessorName and -TemplateName to resolve the template from the src directory automatically.

What structural errors does 1C spreadsheet validation detect?

It detects 12 error types including height smaller than the maximum row index, cell format indices exceeding the format palette, invalid column set references, out-of-bounds named areas and merge ranges, and picture indices referencing nonexistent pictures.

Why does 1C silently ignore Template.xml errors?

The 1C platform tolerates many structural inconsistencies in spreadsheet documents without reporting them, which can cause data loss or layout corruption at runtime. Validating the XML before building catches these issues early.

Can I limit the number of validation errors reported?

Yes, use the -MaxErrors parameter to set the threshold; the default is 20. When the limit is reached, validation stops and prints a message telling you to fix the errors and re-run.

What does the validator exit code mean?

Exit code 0 means all checks passed or only warnings were found. Exit code 1 means at least one structural error was detected, so the script can be integrated into build or CI pipelines.