meta-compile

Convert JSON DSL definitions into 1C metadata XML and configuration exports.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill meta-compile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-compile
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/meta-compile
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill meta-compile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

JSON DSL definitions can be translated into ready-to-use 1C metadata exports (XML + configuration modules) and automatically registered in Configuration.xml.

Core Features & Use Cases

  • Generate 1C metadata objects (Catalogs, Documents, Registers, Enumerations, Constants, and more) from a JSON DSL.
  • Support batch processing by handling an array of objects in a single run, with robust validation and error reporting.
  • Produce a complete export structure (XML, Configuration.xml integration) suitable for deployment in 1C configurations.

Quick Start

Create a JSON file describing your 1C object and run the meta-compile script to generate the export.

Frequently Asked Questions about meta-compile

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

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

You can generate 1C metadata from JSON by defining catalogs, documents, and registers in a JSON DSL file, then running the compile script to produce metadata XML exports and register them in Configuration.xml for deployment.

Can I batch process multiple 1C metadata objects in a single JSON file?

Yes, batch processing 1C metadata is supported by passing an array of objects in a single JSON DSL run. The script validates all inputs and generates complete XML export structures with error reporting for any invalid definitions.

Do I need PowerShell and Python to export 1C configuration metadata from JSON?

Yes, exporting 1C configuration metadata from JSON requires standard PowerShell and Python runtime environments. These runtimes execute the scripts responsible for validating JSON DSL inputs and producing the final XML export structure.

What 1C metadata objects can I create using a JSON DSL?

You can create various 1C metadata objects from a JSON DSL, including Catalogs, Documents, Registers, Enumerations, and Constants. The process outputs the corresponding metadata XML files and updates Configuration.xml for deployment.

What is the best way to automate 1C metadata creation for deployment?

Automating 1C metadata creation is best achieved by defining objects in a JSON DSL and compiling them into XML exports. This produces a complete export structure with Configuration.xml integration, streamlining automated deployment workflows.

Why does my JSON DSL to 1C metadata export fail during validation?

Your JSON DSL to 1C metadata export fails during validation when the input JSON contains malformed definitions or missing required fields for catalogs or documents. The script validates inputs before producing XML and reports errors to identify structural issues.