support-edit

Toggle 1C configuration support states in exported metadata files.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill support-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: support-edit
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/support-edit
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill support-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you change the support status of exported 1C configuration files so you can unlock a specific object for editing, remove it from vendor support, or restore a locked state without editing the metadata by hand.

Core Features & Use Cases

  • Per-object support changes: Switch a catalog, form, layout, or other object between editable, off-support, and locked states.
  • Whole-configuration capability control: Turn the configuration-wide ability to change metadata on or off when the dump is read-only.
  • Safe, targeted updates: The scripts locate the configuration root, resolve object UUIDs, validate the bin format, and avoid unnecessary writes when nothing needs to change.
  • Use case: Use this Skill when a standard 1C configuration arrives “on the lock” and you need to open one object for customization while preserving the rest of the vendor update flow.

Quick Start

Ask the skill to make the chosen 1C object editable on support or to switch the full configuration capability on or off for the exported dump.

Frequently Asked Questions about support-edit

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

FAQPage Schema
How do I unlock a specific 1C configuration object for editing when it is on vendor support?

You can toggle a specific 1C configuration object to editable by locating Configuration.xml, resolving its UUID, and safely rewriting the UTF-8 bin record to change its support state.

Can I change the support state of an exported 1C dump without editing metadata files by hand?

Yes, scripts automatically locate the configuration root, validate the bin format, and safely rewrite UTF-8 bin records to toggle support states for catalogs, forms, and layouts without manual metadata editing.

What is the difference between editable, off-support, and locked states in 1C configuration metadata?

Editable allows object customization, off-support removes the object from the vendor update flow, and locked restores the read-only state. The Skill safely toggles objects between these three support states.

Do I need lxml installed to toggle 1C configuration support states?

Yes, lxml is a required dependency for parsing and rewriting exported 1C configuration metadata files when toggling object support states and dump-level capability flags.

How does a safe no-op handling work when changing 1C configuration support?

The Skill validates the bin format and checks existing flags before writing, avoiding unnecessary file updates when the target object already matches the desired editable, off-support, or locked state.