1c-role-compile

Generate 1C role metadata and Rights.xml files from access rights descriptions.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Jefest9988/1c-ai-development-kit --skill 1c-role-compile-jefest9988
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-role-compile
Source: https://github.com/Jefest9988/1c-ai-development-kit/tree/main/.cursor/skills/1c-roles/compile
Command: npx skills add https://github.com/Jefest9988/1c-ai-development-kit --skill 1c-role-compile-jefest9988

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of 1C role files, including metadata and the Rights.xml file, based on a provided rights description, saving developers significant manual effort in defining access rights.

Core Features & Use Cases

  • Role File Generation: Creates RoleName.xml (metadata) and RoleName/Ext/Rights.xml (rights definition).
  • Structured Rights Definition: Supports common and rare 1C object types and their associated rights.
  • Use Case: When a new user role needs to be defined for a specific set of configuration objects, this Skill can quickly generate the necessary files based on a clear description of required permissions.

Quick Start

Use the 1c-role-compile skill to create a role named 'SalesManager' in the 'Roles/' directory.

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 files from a text description?

You can generate 1C role metadata and Rights.xml files by providing a textual description of access rights, which automates the creation of configuration object permissions and saves manual effort.

What is the best way to define 1C access control for common and nested configuration objects?

Defining 1C access control involves specifying permissions for various configuration object types, including common sets and nested objects, which can be structured automatically from a rights description.

Can I include Row-Level Security templates when creating 1C roles?

Yes, you can incorporate Row-Level Security (RLS) templates when creating 1C roles to define granular access control within the 1C:Enterprise platform.

How does automating role file generation work for 1C:Enterprise configurations?

Automating role file generation for 1C:Enterprise works by taking a clear description of required permissions and outputting the RoleName.xml metadata and RoleName/Ext/Rights.xml files directly.

What limitations exist when defining user access rights for 1C configuration objects?

The primary limitation is that the generated rights must align with supported 1C object types, relying entirely on the accuracy of the textual description provided for the access permissions.