1c-meta-compile

Converts JSON DSL definitions into 1C metadata XML for deployment.

40|11|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-meta-compile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-meta-compile
Source: https://github.com/Desko77/claude-code-skills-1c/tree/main/skills/1c-meta-compile
Command: npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-meta-compile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Converting JSON DSL definitions into 1C metadata XML eliminates manual XML creation, reduces errors, and speeds up configuration deployment.

Core Features & Use Cases

  • Converts JSON DSL definitions into 1C metadata XML for a wide range of object types (Catalog, Document, Enum, InformationRegister, AccumulationRegister, AccountingRegister, CalculationRegister, ChartOfAccounts, ChartOfCharacteristicTypes, ChartOfCalculationTypes, BusinessProcess, Task, ExchangePlan, DocumentJournal, etc.).
  • Supports batch processing (arrays of objects) and Russian-to-English type alias resolution to ensure compatibility with 1C tooling.
  • Validates inputs and outputs well-structured XML with generated internal info for traceability.

Quick Start

Provide a JSON file containing one or more objects and run the meta-compile script to produce the corresponding XML metadata in the specified OutputDir.

Frequently Asked Questions about 1c-meta-compile

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

FAQPage Schema
How do I generate 1C metadata XML from JSON definitions?

Convert JSON DSL definitions into 1C metadata XML by providing a JSON file and running the meta-compile script to produce deployment-ready XML in the specified OutputDir.

What 1C object types can be created from JSON DSL?

JSON DSL supports creating 1C metadata for Catalogs, Documents, Enums, InformationRegisters, AccumulationRegisters, AccountingRegisters, CalculationRegisters, ChartsOfAccounts, BusinessProcesses, Tasks, ExchangePlans, and DocumentJournals.

Does 1C metadata generation support batch processing multiple objects?

Batch processing is supported by passing arrays of objects in your JSON DSL, allowing multiple 1C metadata XML files to be generated in a single execution.

How does Russian-to-English type alias resolution work in 1C code generation?

Russian-to-English type alias resolution translates Russian type names in your JSON DSL into English equivalents, ensuring generated metadata compatibility with 1C tooling.

Why manually creating 1C configuration XML instead of using a JSON DSL?

Manually creating 1C configuration XML is error-prone, whereas converting JSON DSL definitions eliminates manual creation, validates inputs, and accelerates configuration deployment.