interface-validate

Validates 1C:Enterprise CommandInterface.xml files for structural errors and duplicate command references.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually checking 1C:Enterprise subsystem command interface XML files for structural mistakes is slow and error-prone. This Skill validates CommandInterface.xml files automatically, catching root element errors, invalid sections, ordering issues, malformed command references, and duplicates before they break the subsystem UI. ## Core Features & Use Cases - Structural XML validation: Checks the root element, allowed sections, element ordering, and command reference formats in CommandInterface.xml. - Duplicate detection: Finds duplicate entries in the command interface definition. - Flexible input: Accepts either a subsystem catalog path (e.g. Subsystems/Продажи) or a direct path to the CommandInterface.xml file. - Configurable output: Optional detailed mode listing all checks including successful ones, plus a MaxErrors limit (default 30) to stop after N errors. - Use Case: After configuring the command interface of a 1C subsystem, run the validation to confirm the XML is correct before committing changes to the configuration repository. ## Quick Start Ask the assistant to validate the command interface of your subsystem, for example: run interface validation on Subsystems/Продажи with detailed output.

Frequently Asked Questions about interface-validate

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

FAQPage Schema
How do I validate a 1C CommandInterface.xml file?▼

Call the unica.interface.validate MCP tool with the CIPath parameter pointing to either the subsystem catalog (e.g. Subsystems/Продажи) or the direct path to CommandInterface.xml. The tool checks structure, sections, ordering, references, and duplicates.

What errors does 1C command interface validation detect?▼

It detects incorrect root elements, disallowed sections, wrong element ordering, malformed command reference formats, and duplicate entries in the CommandInterface.xml file.

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

Yes, use the MaxErrors parameter to stop validation after a specified number of errors. The default limit is 30 errors.

How do I see all validation checks including successful ones?▼

Pass the Detailed flag when calling the validation. Detailed mode outputs every check performed, including the ones that passed, instead of only reporting failures.

Does the validation accept a subsystem folder instead of the XML file path?▼

Yes, CIPath accepts either a subsystem catalog path such as Subsystems/Продажи or a direct path like Subsystems/Продажи/Ext/CommandInterface.xml. Both forms are resolved by the unica MCP tool.