subsystem-validate

Validate 1C subsystem XML structures and child references.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill subsystem-validate-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subsystem-validate
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/subsystem-validate
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill subsystem-validate-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

This Skill checks whether a 1C subsystem export is structurally correct so you can catch XML mistakes, missing properties, and broken child references before they reach production.

Core Features & Use Cases

  • Validates the root metadata object, UUID, required properties, booleans, content references, and optional command interface file.
  • Detects duplicate content entries and duplicate child subsystems, and warns when referenced child XML files are missing.
  • Use it after creating or editing a subsystem export to confirm the structure is ready for import or further processing.

Quick Start

Ask the skill to validate the subsystem XML path you want checked and return a concise report of errors, warnings, and file-level issues.

Frequently Asked Questions about subsystem-validate

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

FAQPage Schema
How do I validate 1C subsystem XML structures before importing them?

You can validate 1C subsystem XML structures by running a dedicated script that checks the MetaDataObject/Subsystem root, verifies UUIDs and property formats, and detects duplicate or missing child objects to ensure the export is structurally correct.

What is checked during 1C subsystem metadata validation?

1C subsystem metadata validation checks the root metadata object, UUID formats, required properties, booleans, and content references. It also detects duplicate content entries, duplicate child subsystems, and warns when referenced child XML files are missing.

Do I need lxml to validate 1C configuration subsystem exports?

Yes, you need the lxml library installed to validate 1C configuration subsystem exports. The validation scripts depend on lxml to parse well-formed XML and analyze the subsystem hierarchy and command interface metadata.

Why does my 1C subsystem validation fail on missing child objects?

1C subsystem validation fails on missing child objects when referenced child XML files are absent from the export package. The validator checks the child hierarchy and warns when expected subsystem files are missing.

Can I check for duplicate content entries in a 1C subsystem XML file?

Yes, you can check for duplicate content entries in a 1C subsystem XML file using a validation script. It detects duplicate content references and duplicate child subsystems, ensuring the metadata structure is clean and ready for processing.