What problem does it solve? After creating or modifying a 1C:Enterprise subsystem, developers need to verify that the subsystem's XML definition is structurally correct before continuing work. This Skill runs validation against the subsystem XML from a configuration dump and reports errors without manual inspection. ## Core Features & Use Cases - Subsystem XML validation: Checks the structural correctness of a subsystem XML file from a configuration export via the unica.subsystem.validate MCP tool. - Flexible target selection: Accepts either a file path (SubsystemPath) or a logical selector (sourceSet + metadataPath, e.g. Subsystem.<Name>); passing both is rejected with a selector_conflict error. - Configurable output: Supports a Detailed flag to show all checks including successful ones, and MaxErrors (default 30) to stop after a given number of errors. - Use Case: After editing the Продажи subsystem in a 1C configuration dump, run validation on Subsystems/Продажи to confirm the XML structure is correct before committing changes. ## Quick Start Validate the 1C subsystem at Subsystems/Продажи and show me any structural errors found.