cf-validate

Validates 1C:Enterprise configuration XML files for structural errors via the unica MCP tool.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill cf-validate-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cf-validate
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/cf-validate
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill cf-validate-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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 after modifying it?▼

Call the unica.cf.validate MCP tool with the ConfigPath argument pointing to your Configuration.xml file or its upload directory. The tool checks XML well-formedness, properties, enum values, ChildObjects, and related files, reporting up to 30 errors by default.

What does 1C Configuration.xml validation check?▼

Validation checks XML well-formedness, InternalInfo, configuration properties, enum values, ChildObjects structure, DefaultLanguage, language files, and object catalogs. Use the Detailed flag to also see all successful checks in the output.

Can I validate a 1C configuration by source set name instead of a file path?▼

Yes, pass the sourceSet argument with a source set name from v8project.yaml instead of ConfigPath. Exactly one selector is required; passing both is rejected with a selector_conflict error code.

Why does validation fail with a selector_conflict error?▼

The selector_conflict error occurs when both ConfigPath and sourceSet are provided in the same call. The tool accepts exactly one target selector, so remove one of the two arguments and retry.

How do I limit the number of errors reported during 1C validation?▼

Set the MaxErrors parameter to the desired count; validation stops after that many errors. The default limit is 30 errors per run.