mxl-validate

Validate 1C spreadsheet Template.xml structure and palette references.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill mxl-validate-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxl-validate
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/mxl-validate
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill mxl-validate-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents broken 1C spreadsheet (MXL) templates by detecting structural issues in Template.xml before they reach runtime or confuse editors.

Core Features & Use Cases

  • Checks template structure: validates height vs. defined row indices, row/cell column bounds, and merge bounds.
  • Verifies palette references: ensures indices for fonts, formats, lines/borders, pictures are within declared palette sizes.
  • Validates named areas: checks begin/end row limits and referenced columnsID existence for named cell areas.
  • Use Case: after editing a layout macro-like template for printed forms, run this validation to catch out-of-range indices and invalid references early.

Quick Start

Run the mxl-validate skill with the path to your Template.xml (or its template folder) to get a pass/fail report with detected errors and warnings.

Frequently Asked Questions about mxl-validate

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

FAQPage Schema
How do I validate a 1C MXL spreadsheet template before loading it into 1C?

To validate a 1C MXL spreadsheet template, run a validation check against the Template.xml file located under Templates/<Name>/Ext to verify internal consistency of rows, columns, merges, and palette index references before loading it into 1C.

What structural issues cause broken 1C spreadsheet templates during runtime?

Broken 1C spreadsheet templates are typically caused by out-of-range indices and invalid references, such as row heights mismatching defined row indices, merge bounds exceeding column limits, and palette references exceeding declared sizes for fonts, formats, or borders.

Can I check named areas and palette references in a Template.xml file automatically?

Yes, you can automatically check named areas and palette references in a Template.xml file by parsing the XML with spreadsheet namespaces to verify begin/end row limits, columnsID existence, and ensure picture, font, and line indices are within declared palette sizes.

When should I run template validation on my 1C MXL layout for printed forms?

You should run template validation on your 1C MXL layout immediately after creating or modifying a template for printed forms to catch structural defects and enforce index and size bounds before the file reaches runtime or confuses editors.

Does the 1C MXL template validator require specific dependencies or environments?

The 1C MXL template validator requires no external dependencies, but needs you to locate and normalize the Template.xml file under Templates/<Name>/Ext to properly parse the XML with spreadsheet namespaces and return a non-zero exit status when errors exceed zero.