1c-metadata-manage
1C Metadata Manage — Skill Dispatch
Use this skill when the task involves 1C metadata structure (creating, editing, validating, or removing configuration objects, forms, reports, layouts, roles, extensions, or databases).
Hard rule
Any mutation of metadata XML — Configuration.xml, object XML, Form.xml, MXL / SKD layouts, Role.xml, subsystems, command interfaces — is executed through this skill (dispatch below → domain doc → PowerShell tools) or through the 1c-metadata-manager subagent. The tools under tools/ handle BOM, encodings, UUID regeneration, ChildObjects ordering and cross-references that are easy to break manually. Hand-editing these files while the skill is available is a defect (AGENTS.md → Skills and Subagents), not a slower-but-acceptable alternative.
The same gate covers infobase operations (create / run, load / dump configuration, /UpdateDBCfg, web publication): use the db-ops / web-ops tools of this skill (db-manage.md, web-manage.md) or the matching slash command (/update1cbase, /loadfrom1cbase, /getconfigfiles, /deploy-and-test) — never an ad-hoc 1cv8.exe / ibcmd command line composed from memory. DB updates follow the iterative retry discipline (db-manage.md → Update retry discipline).
The only exceptions:
- Unambiguous one-line fix of an existing value that cannot break structure — a synonym / comment typo, a boolean flag flip on an existing element. Anything that adds / removes / reorders elements, touches UUIDs, or spans more than one line of XML is not "one-line".
- Skill not available in the session (files not installed / not exposed) — state it once in one line, then hand-edit with
metadata-xml-workarounds.mdloaded and validate perverification-gates.md → Gate 5. - Read-only analysis of metadata XML is not a mutation — reading files directly is fine (subject to
mcp-first-search.mdfor locating them).
Vendor support gate
Every mutating tool of this skill refuses to edit an object of a typical configuration on vendor support that is locked ("на замке"), and refuses to delete one that has not been taken off support. This is not advisory: the run exits 1 with a diagnostic. Editing such an object directly breaks future vendor updates silently, so the refusal is the correct outcome, not an obstacle to route around by hand-editing the XML.