What problem does it solve? After creating or modifying a 1C:Enterprise configuration extension (CFE), developers need to verify its structural correctness before deployment. This Skill checks the extension's XML format, properties, composition, and borrowed objects, catching errors early in the development cycle. ## Core Features & Use Cases - Extension Structure Validation: Checks XML format, properties, and composition of a CFE directory or its Configuration.xml file. - Configurable Error Reporting: Supports detailed output of all checks and a maximum error limit (default 30) to control report size. - MCP Integration: Routes validation through the unica MCP tool unica.cfe.validate, which manages XML/JSON DSL work and refreshes workspace caches. - Use Case: After editing an extension that borrows catalog objects from a base configuration, run validation on the extension directory to confirm the borrowed objects and properties are structurally correct before applying the extension. ## Quick Start Ask the assistant to validate the 1C configuration extension located in the src directory using cfe-validate.