dcs-validate

Validates 1C:Enterprise Data Composition Schema templates for structural correctness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After creating or modifying a 1C:Enterprise Data Composition Schema (СКД), developers need to verify that the Template.xml is structurally correct before deployment. This Skill checks the schema for format errors, broken references, and duplicate names, catching defects early in the development cycle. ## Core Features & Use Cases - Structural validation of СКД templates: Checks Template.xml files for format errors, broken links, and duplicate names via the unica.dcs.validate MCP tool. - Flexible target selection: Accepts either a file path (TemplatePath) or a logical selector (sourceSet + metadataPath), with exactly one selector enforced per call. - Configurable output: Supports detailed reporting of all checks and a MaxErrors limit to stop after a defined number of failures. - Use Case: After editing a report's data composition schema in a 1C configuration project, run validation against the template directory to confirm no broken field references or duplicate names were introduced before committing. ## Quick Start Validate the data composition schema template at src/МойОтчёт/Templates/ОсновнаяСхема and show me any structural errors found.

Frequently Asked Questions about dcs-validate

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

FAQPage Schema
How do I validate a 1C Data Composition Schema (СКД) template?▼

Call the unica.dcs.validate MCP tool with the TemplatePath pointing to your Template.xml file or its template directory. The tool checks structural correctness, broken references, and duplicate names, returning up to 20 errors by default.

How to check a 1C report template for broken references after editing?▼

Run validation immediately after modifying the schema by passing the template directory path to unica.dcs.validate. It detects broken links and duplicate names introduced by your edits, and the Detailed flag shows all checks including successful ones.

Can I validate a 1C schema by metadata path instead of file path?▼

Yes, pass sourceSet and metadataPath (for example Report.<Отчёт>.Template.<Макет>) instead of TemplatePath. Exactly one selector type is allowed per call; providing both is rejected with a selector_conflict error.

Why does validation fail with a selector_conflict error?▼

The selector_conflict error occurs when both a file path (TemplatePath) and a logical selector (sourceSet plus metadataPath) are provided in the same call. Remove one of the selectors so exactly one targeting method remains.

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

Set the MaxErrors parameter to stop validation after a specified number of errors; the default limit is 20. This is useful for large schemas where you want to fix issues incrementally.