What problem does it solve? Defining access rights in 1C:Enterprise requires hand-writing verbose XML files (role metadata and Rights.xml) with correct namespaces, right names per object type, and RLS templates, which is error-prone when done manually. ## Core Features & Use Cases - Role File Generation: Creates the role metadata XML (with generated UUID) and the Ext/Rights.xml file, plus registration in Configuration.xml ChildObjects. - Rights Reference Tables: Provides ready-made right sets (Read/Full) for catalogs, documents, registers, and simple types, including nested objects and configuration-level rights. - RLS Support: Includes the restrictionByCondition syntax and restriction templates for row-level security on Read, Update, Insert, and Delete rights. - Use Case: You need a role for a scheduled job that reads currencies and updates exchange rates. The skill produces the exact Rights.xml with only programmatic rights (no Interactive/View rights), ready to load into the configuration. ## Quick Start Ask the agent to create a 1C role named RatesUpdater in the Roles directory with read access to the Currencies catalog and read-write access to the CurrencyRates information register.
