mxl-info

Analyze MXL Template.xml to list named areas, parameters, and column sets.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill mxl-info
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxl-info
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/source/mxl-info
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill mxl-info

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Quickly understand the structure of an MXL layout by reading Template.xml and listing named areas, parameters, and column sets, saving time from manual XML inspection.

Core Features & Use Cases

  • Analyze a Template.xml to produce a concise summary of named areas, their types and coordinates, along with parameter and column-set information.
  • Output results in text or JSON for easy consumption by other tools and automation.
  • Use before implementing data extraction or UI logic in 1C 8.3, debugging layouts, or validating templates.

Quick Start

Provide the path to Template.xml via -TemplatePath and run the tool to generate a summary.

Frequently Asked Questions about mxl-info

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

FAQPage Schema
How do I summarize named areas and parameters in a 1C MXL Template.xml?

You can summarize an MXL Template.xml by providing the -TemplatePath parameter to extract and list named areas, parameters, and column sets into a concise structured text or JSON overview.

What is the best way to inspect MXL layout structure before implementing data extraction?

The best way to inspect MXL layout structure is analyzing Template.xml to list named areas, their types, coordinates, and column sets, providing a quick macro-level understanding before writing data extraction or UI logic.

Can I output MXL template analysis results in JSON for downstream automation?

Yes, you can output MXL template analysis results in JSON format, enabling downstream tooling and automation to easily consume the summarized named areas, parameters, and column sets.

Does the MXL template summarizer support identifying layouts by processor name instead of file path?

Yes, the MXL template summarizer supports identifying layouts by passing -ProcessorName plus -TemplateName as an alternative to providing the direct -TemplatePath file location.

Why manually inspect XML when debugging 1C 8.3 layouts instead of using a summarizer?

Manually inspecting XML for 1C 8.3 layouts is time-consuming; a summarizer quickly reads Template.xml to validate templates and extract named areas, parameters, and column sets, saving significant debugging time.