subsystem-edit

Edits 1C:Enterprise subsystem XML files to manage content, child subsystems, and properties.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying 1C:Enterprise subsystem definitions by hand-editing XML is error-prone and tedious. This Skill performs targeted edits to a subsystem's XML file through the unica MCP tool, so you can add or remove metadata objects, manage child subsystems, and change properties without touching raw XML. ## Core Features & Use Cases - Content management: Add or remove objects (catalogs, documents, reports) from a subsystem's Content section, individually or in batches. - Child subsystem management: Add or remove nested subsystems in the ChildObjects section. - Property editing: Change subsystem properties such as Synonym, IncludeInCommandInterface, and UseOneCommand. - Safe mutations: Changes run as a dry run by default and only apply when you explicitly pass dryRun: false; built-in validation checks correctness for platform 8.3.27 before committing. - Use Case: You need to expose the "Номенклатура" catalog under the "Продажи" subsystem. Invoke the skill with SubsystemPath pointing at the subsystem, Operation "add-content", and Value "Catalog.Номенклатура" to update the XML in one call. ## Quick Start Ask the assistant to add the catalog "Номенклатура" to the "Продажи" subsystem in your 1C configuration using the subsystem-edit skill with dry run disabled.

Frequently Asked Questions about subsystem-edit

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

FAQPage Schema
How do I add an object to a 1C subsystem?▼

Call the unica.subsystem.edit MCP tool with the SubsystemPath pointing to the subsystem, Operation set to add-content, and Value set to the object name such as Catalog.Номенклатура. You can pass a single object or a JSON array to add several objects at once.

How do I change subsystem properties in 1C configuration XML?▼

Use the set-property operation with a Value containing a JSON object with name and value fields, for example {"name":"IncludeInCommandInterface","value":"false"}. The edit is applied to the subsystem XML through the unica MCP tool.

Does subsystem-edit apply changes immediately or is there a dry run?▼

Mutations run as a dry run by default. Changes are only committed when you explicitly pass dryRun: false, and mandatory validation against platform 8.3.27 correctness rules runs before any change is fixed.

Can I edit a subsystem that is locked by vendor support in 1C?▼

The vendor support guard inside unica blocks edits to locked or read-only supported objects. In that case, use a CFE extension or an explicit support-state change plan instead of editing raw support metadata.

What operations does the 1C subsystem editor support?▼

It supports five operations: add-content and remove-content for managing objects in the Content section, add-child and remove-child for nested subsystems, and set-property for changing properties such as Synonym or UseOneCommand.