subsystem-validate

Validates structural correctness of 1C:Enterprise subsystem XML files from configuration dumps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After creating or modifying a 1C:Enterprise subsystem, developers need to verify that the subsystem's XML definition is structurally correct before continuing work. This Skill runs validation against the subsystem XML from a configuration dump and reports errors without manual inspection. ## Core Features & Use Cases - Subsystem XML validation: Checks the structural correctness of a subsystem XML file from a configuration export via the unica.subsystem.validate MCP tool. - Flexible target selection: Accepts either a file path (SubsystemPath) or a logical selector (sourceSet + metadataPath, e.g. Subsystem.<Name>); passing both is rejected with a selector_conflict error. - Configurable output: Supports a Detailed flag to show all checks including successful ones, and MaxErrors (default 30) to stop after a given number of errors. - Use Case: After editing the Продажи subsystem in a 1C configuration dump, run validation on Subsystems/Продажи to confirm the XML structure is correct before committing changes. ## Quick Start Validate the 1C subsystem at Subsystems/Продажи and show me any structural errors found.

Frequently Asked Questions about subsystem-validate

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

FAQPage Schema
How do I validate a 1C subsystem XML file?▼

Call the unica.subsystem.validate MCP tool with the SubsystemPath argument pointing to the subsystem directory or XML file, for example Subsystems/Продажи or Subsystems/Продажи.xml. The tool checks the structural correctness of the subsystem definition from the configuration dump.

How to validate a 1C subsystem by logical metadata address instead of file path?▼

Pass sourceSet and metadataPath arguments instead of SubsystemPath, for example metadataPath set to Subsystem.<Name>. The source set name comes from unica.project.map and the address from unica.source.resolve.

Can I pass both a file path and a metadata address for subsystem validation?▼

No, exactly one target selector is allowed. Providing both SubsystemPath and the sourceSet plus metadataPath combination is rejected with a selector_conflict error code as defined in ADR-0049.

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

Set the MaxErrors parameter to stop validation after a given number of errors; the default is 30. Use the Detailed flag if you also want to see all checks, including successful ones.

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

Run it after creating or modifying a subsystem in the configuration dump to confirm the XML structure is correct. It is intended as a post-change verification step before continuing development or committing changes.