cf-validate

Validate 1C Configuration.xml structural integrity and language resources.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill cf-validate-msrv-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cf-validate
Source: https://github.com/msrv-tech/skills/tree/main/cf-validate
Command: npx skills add https://github.com/msrv-tech/skills --skill cf-validate-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

Validates a 1C Configuration.xml for structural integrity after creating or modifying a configuration.

Core Features & Use Cases

  • XML structural validation: ensures well-formed Configuration.xml and correct top-level structure.
  • InternalInfo and ClassIds checks: verifies 7 ContainedObject entries with known ClassIds and valid ObjectId values.
  • Properties and language support: checks Name, DefaultLanguage, and DefaultRunMode, plus language file existence and object directory presence.
  • Use Case: run during configuration release cycles to catch misconfigurations and missing language resources before publishing.

Quick Start

Run the cf-validate script against your Configuration.xml to perform all checks, for example with -ConfigPath upload/Configuration.xml.

Frequently Asked Questions about cf-validate

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

FAQPage Schema
How do I validate a 1C Configuration.xml file for structural integrity?▼

To validate a 1C Configuration.xml, run the cf-validate script with your configuration path to check XML well-formedness, InternalInfo ContainedObject entries, Properties values, and language files. It produces a detailed report and optional OutFile output.

What does checking a 1C Configuration.xml typically include?▼

Checking a 1C Configuration.xml involves verifying XML well-formedness, 7 ContainedObject ClassIds and ObjectId values, Properties like Name and DefaultLanguage, default language files, and object directory presence to catch misconfigurations before publishing.

When do I need to validate a 1C Configuration.xml?▼

You need to validate a 1C Configuration.xml after creating or modifying a configuration, typically during release cycles, to detect structural misconfigurations and missing language resources before publishing the configuration.

Can I run configuration validation using PowerShell instead of Python?▼

Yes, you can run configuration validation using either cf-validate.py or cf-validate.ps1. Both scripts perform the same structural checks on a 1C Configuration.xml and generate a report with optional OutFile output.

Do I need lxml to validate Configuration.xml files?▼

Yes, the lxml dependency is required to run the Python validation script. It provides the underlying XML parsing capabilities needed to check the Configuration.xml structure and generate the validation report.