1c-role-compile

Generate 1C role metadata and Rights.xml templates from a rights description.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill 1c-role-compile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-role-compile
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/skills/1c-role-compile
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill 1c-role-compile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of 1C role metadata and Rights.xml from a rights description, eliminating manual XML composition.

Core Features & Use Cases

  • Generates Roles/RoleName.xml metadata with Name, Synonym, and UUID placeholders
  • Creates Roles/RoleName/Ext/Rights.xml with a ready Rights template and structure
  • Provides clear guidance for registering the role in Configuration.xml and linking objects

Quick Start

Run 1c-role-compile <RoleName> <RolesDir> to generate Roles/RoleName.xml and Roles/RoleName/Ext/Rights.xml from a rights description.

Frequently Asked Questions about 1c-role-compile

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

FAQPage Schema
How do I generate 1C role metadata and Rights.xml automatically?

Generate 1C role metadata and Rights.xml automatically by running the compile command with a role name and roles directory, which creates RoleName.xml and Ext/Rights.xml templates with UUID placeholders from your rights description.

What is the best way to create a Rights.xml template for 1C configuration objects?

Creating a Rights.xml template for 1C configuration objects involves applying a ready rights template to the Roles directory structure, yielding a structured file with predefined access rights ready to apply.

Can I use this to define access rights for 1C configurations without manual XML composition?

Yes, you can define access rights for 1C configurations without manual XML composition by providing a rights description, which the tool transforms into structured metadata files and Rights.xml templates.

Do I need to register generated 1C roles in Configuration.xml manually?

Yes, you need to register generated 1C roles in Configuration.xml manually, as the generation process provides clear guidance for linking objects and registering the role within your configuration.

What structure does the generated 1C role metadata follow?

The generated 1C role metadata follows the Roles directory structure, producing a root RoleName.xml with Name, Synonym, and UUID placeholders, alongside a nested Ext/Rights.xml containing the rights template.

Are there limitations when generating UUID placeholders for 1C roles?

The generated 1C role files include UUID placeholders that must be manually replaced or managed, meaning the output serves as a ready-to-apply template rather than a finalized configuration with hardcoded unique identifiers.