What problem does it solve? After creating or modifying a 1C:Enterprise configuration, developers need to verify that Configuration.xml and its related files are structurally correct before proceeding. This Skill checks XML well-formedness, InternalInfo, properties, enum values, ChildObjects, DefaultLanguage, language files, and object catalogs, catching errors early. ## Core Features & Use Cases - Structural validation of Configuration.xml: Checks XML well-formedness, InternalInfo, properties, enum values, ChildObjects, DefaultLanguage, language files, and object catalogs. - Flexible target selection: Accepts either a file path (ConfigPath pointing to Configuration.xml or an upload directory) or a logical sourceSet name from v8project.yaml, with exactly one selector required. - Configurable output: Detailed mode shows all checks including successful ones, and MaxErrors limits how many errors are reported before stopping (default 30). - Use Case: After editing a 1C configuration's metadata objects, run validation against the upload directory to confirm the configuration structure is intact before committing changes. ## Quick Start Ask the assistant to validate the 1C configuration located in your upload directory using the cf-validate skill.