support-edit

Changes vendor support state of 1C:Enterprise configuration objects via the unica MCP tool.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying a vendor-supplied 1C:Enterprise configuration requires explicitly changing support states, and editing Ext/ParentConfigurations.bin by hand is error-prone. This Skill routes all support-state changes through the unica.support.edit MCP tool with safe dry-run defaults. ## Core Features & Use Cases - Global capability toggle: Turn configuration editing on or off with the Capability parameter while keeping vendor objects locked. - Per-object rules: Set an individual object to editable, off-support, or locked using the Set parameter. - Safe mutation flow: Mutations default to dryRun: true; real changes require explicit user confirmation, with unica.cf.info / unica.meta.info checks before and after. - Use Case: You need to customize one vendor catalog without losing support on the rest of the configuration — enable editing globally, then set only Catalogs/Items.xml to editable. ## Quick Start Ask the assistant to enable editing for the configuration in src/configuration and set the Items catalog to editable using the unica support edit tool, confirming the change so it runs without dry run.

Frequently Asked Questions about support-edit

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

FAQPage Schema
How do I enable editing of a vendor 1C configuration?▼

Call the unica.support.edit MCP tool with the Path pointing to your configuration dump and Capability set to on. This enables global editing while keeping vendor objects locked, and the change runs as a dry run until you pass dryRun false.

How to make a single 1C configuration object editable without removing support?▼

Use unica.support.edit with Path pointing to the object XML, such as src/configuration/Catalogs/Items.xml, and Set equal to editable. This changes only that object's rule while preserving vendor support for the rest of the configuration.

What is the difference between Capability and Set parameters in support editing?▼

Capability toggles the global editing capability of the whole configuration with values on or off. Set changes the support rule of one selected object to editable, off-support, or locked. You must provide exactly one of the two parameters per call.

Why does setting an object to editable fail in 1C support edit?▼

Object-level Set operations fail if global editing capability has not been enabled first with Capability on. The tool also stops if the target object cannot be resolved to a UUID, in which case inspect it with unica.meta.info or unica.form.info before retrying.

Should I edit ParentConfigurations.bin manually to change 1C support state?▼

No, manual editing of Ext/ParentConfigurations.bin is explicitly prohibited. All support-state changes should go through the unica.support.edit MCP tool, which validates the operation and defaults to a safe dry run.