cfe-validate

Validates 1C:Enterprise configuration extension structure, XML format, and borrowed objects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about cfe-validate

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

FAQPage Schema
How do I validate a 1C configuration extension (CFE)?▼

Run the cfe-validate skill with the ExtensionPath parameter pointing to the extension directory or its Configuration.xml file. It calls the unica MCP tool unica.cfe.validate, which checks XML format, properties, composition, and borrowed objects.

What does CFE validation check in 1C extensions?▼

It verifies structural correctness of the extension: XML format validity, property definitions, overall composition, and borrowed objects taken from the base configuration. It is the extension counterpart of configuration validation.

Can I limit the number of errors reported during extension validation?▼

Yes, use the MaxErrors parameter to stop validation after a specified number of errors; the default is 30. You can also pass the Detailed flag to see all checks, including successful ones.

When should I run CFE validation in a 1C development workflow?▼

Run it after creating or modifying an extension, before applying or deploying it. Early validation catches structural issues in XML and borrowed objects before they cause failures in the infobase.

Does cfe-validate modify the extension during validation?▼

Validation itself is a read operation. For any mutating operations routed through the unica MCP orchestrator, dryRun remains enabled by default unless the user explicitly requests the change with dryRun set to false.