meta-edit

Applies typed atomic edits to existing 1C:Enterprise metadata objects via the unica.meta.edit MCP tool.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing existing 1C:Enterprise metadata objects by hand-editing XML files is error-prone and breaks vendor support boundaries. This Skill routes all changes through the typed unica.meta.edit MCP operation, which applies ordered operations atomically in one transaction and returns a preview before anything is written. ## Core Features & Use Cases - Typed atomic operations: setProperties, add, update, remove, and editRelations applied in a single transaction against a sourceSet plus metadataPath address. - Preview-first workflow: every call defaults to dryRun preview with normalized semantic effects per operationIndex; changes publish only when the user explicitly requests dryRun false. - Rich collection support: attributes with tabular section scoping, predefinedItems for catalogs and charts of accounts/characteristic types/calculation types, and typed relations such as owners, registerRecords, basedOn, and event subscription sources. - Use Case: Add a typed string attribute to Catalog.Контрагенты, update a tabular section attribute on Document.ЗаказПокупателя, and atomically replace an event subscription's source, event, and handler, all validated against the published operation schema. ## Quick Start Ask the assistant to use the unica meta-edit skill to add a new string attribute named Комментарий to Catalog.Контрагенты and show the preview before applying.

Frequently Asked Questions about meta-edit

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

FAQPage Schema
How do I edit 1C:Enterprise metadata objects programmatically?▼

Call the unica.meta.edit MCP tool with a sourceSet, metadataPath, and an ordered operations array using setProperties, add, update, remove, or editRelations. All operations in one call apply atomically in a single transaction, and the default dryRun mode returns a preview before publishing.

How do I add a predefined item to a 1C catalog?▼

Use the add operation with collection predefinedItems and typed elements containing id, name, code, and description. This collection is available only for Catalog, ChartOfAccounts, ChartOfCharacteristicTypes, and ChartOfCalculationTypes, with owner-specific extra fields such as isFolder or accountType.

Does unica.meta.edit apply changes immediately?▼

No. Every call defaults to dryRun true, returning normalized semantic effects per operationIndex instead of writing changes. Pass dryRun false only when the user explicitly asks to apply the edit, and check structuredContent.data.validation for diagnostics.

Can I edit metadata objects under vendor support in 1C?▼

Direct edits to vendor-locked objects are blocked by the vendor support guard inside unica. For closed objects, use the CFE/release-support flow through a configuration extension rather than editing the service files directly.

What are the limitations of the unica.meta.edit typed writer?▼

One call modifies one object only, and scenarios without a published typed variant are unsupported, including nested HTTP service URL templates, web service operations, schedules, and shorthand index flags. If the schema does not cover a case, the remaining step must be done in Designer.