1c-subsystem-compile

Generate 1C subsystem XML from JSON and register it in the configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Creating a 1C subsystem is error-prone and repetitive. This Skill automatically generates the XML metadata for a new Subsystem from a JSON definition, ensuring consistent structure and proper registration.

Core Features & Use Cases

  • Generates {OutputDir}/Subsystems/{Name}.xml for top-level subsystems and creates nested Subsystems folders when needed.
  • Registers the new subsystem in Configuration.xml or in a parent subsystem's <ChildObjects> to ensure it appears in the configuration.
  • Supports optional fields such as content, children, synonyms, and pictures to model complete 1C metadata and relationships.

Quick Start

Provide a JSON definition with at least a name and run the subsystem-compile script with -OutputDir and -DefinitionFile or -Value.

Frequently Asked Questions about 1c-subsystem-compile

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

FAQPage Schema
How do I automate 1C subsystem creation from a JSON definition?

You can automate 1C subsystem creation by providing a JSON definition with at least a name and running the compile script with an output directory. The script generates the subsystem XML and registers it in the configuration.

How does registering a new 1C subsystem in Configuration.xml work?

Registering a new 1C subsystem involves generating a Subsystems/{Name}.xml file and adding an entry to Configuration.xml. For nested subsystems, the tool registers the new subsystem within the parent subsystem's ChildObjects section.

Can I model nested 1C subsystems and include synonyms or pictures in the JSON definition?

Yes, the JSON definition supports optional fields including children, synonyms, content, and pictures. This allows you to model complete 1C metadata relationships, including nested parent-child subsystem structures.

What's the best way to generate 1C metadata XML for enterprise configurations?

Generating 1C metadata XML through an automated JSON-driven script ensures consistent structure and proper registration. This approach eliminates repetitive manual tasks and reduces configuration errors when adding top-level or nested subsystems.

Do I need to provide a definition file or can I pass the 1C subsystem JSON inline?

You can provide the 1C subsystem definition either by passing a file path using the -DefinitionFile parameter or by passing the JSON string directly using the -Value parameter. You must also specify an -OutputDir.

Why does my generated 1C subsystem not appear in the configuration?

A generated 1C subsystem might not appear if it was not properly registered in Configuration.xml or the parent's ChildObjects. The script handles this automatically, ensuring the generated XML is referenced correctly in the configuration structure.