meta-remove

Removes 1C:Enterprise metadata objects with reference analysis and atomic publication.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deleting a metadata object in a 1C:Enterprise configuration is risky: other objects may reference it, vendor support locks may block changes, and partial edits can corrupt the source tree. This Skill performs safe removal through the Unica MCP server with a typed dry-run plan before any change is published. ## Core Features & Use Cases - Reference analysis: Runs with dryRun enabled by default to inspect dependencies, diagnostics, and a typed removal plan before applying anything. - Guarded forced removal: Applying a removal when references exist requires triple confirmation (force: true, confirm: true, dryRun: false), preventing accidental destructive changes. - Atomic publication with vendor guard: Vendor support checks run before publication, and changes are published atomically rather than by editing service files directly. - Use Case: You need to delete an obsolete catalog Catalog.Устаревший from a source set. First call unica.meta.remove with dryRun: true to review the removeObject effect and any references, then apply with dryRun: false once the plan is clean. ## Quick Start Ask the assistant to remove the metadata object Catalog.Устаревший from the main source set using the meta-remove skill, starting with a dry run to review references.

Frequently Asked Questions about meta-remove

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

FAQPage Schema
How do I safely delete a 1C metadata object?▼

Call unica.meta.remove with the sourceSet and metadataPath, keeping dryRun enabled first. Review the typed plan, dependencies, and diagnostics in structuredContent.data, then apply with dryRun set to false once the plan is acceptable.

How to remove a 1C catalog that still has references?▼

Forced removal with existing references requires triple confirmation: force set to true, confirm set to true, and dryRun set to false. Without all three, the tool refuses to apply the removal when references are found.

What is the sourceSet parameter in unica.meta.remove?▼

sourceSet is the name of a source set defined in v8project.yaml, not a fixed constant. Retrieve available names with unica.project.map; the value "main" in examples is illustrative, not a default.

Can I bypass the vendor support lock by editing files directly?▼

No. The vendor support guard runs before publication, and a locked object cannot be bypassed by directly editing service files. The removal must go through the guarded MCP workflow.

What does the dry-run preview of meta-remove return?▼

The preview returns a single semantic removeObject effect in structuredContent.data.effects, not the full XML of the deleted object. Success or failure is indicated by structuredContent.ok, with details in structuredContent.data.