1c-role-compile

Generate 1C Role.xml and Rights.xml from JSON DSL definitions.

40|11|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-role-compile-desko77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-role-compile
Source: https://github.com/Desko77/claude-code-skills-1c/tree/main/skills/1c-role-compile
Command: npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-role-compile-desko77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Creates 1C roles quickly by converting JSON DSL definitions into Role.xml metadata and Ext/Rights.xml, automating rights assignment and configuration updates.

Core Features & Use Cases

  • Generates Role.xml and Ext/Rights.xml from JSON role definitions, including object rights and presets.
  • Automatically updates Configuration.xml to register new roles.
  • Validates rights, supports nested objects and presets, and provides a straightforward migration path from JSON to 1C permissions.

Quick Start

Describe a role in JSON and run the role-compile skill to generate Role.xml and Rights.xml, then integrate them into the project.

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 roles from JSON definitions?

To generate 1C roles from JSON definitions, you describe your role permissions in a JSON DSL and run the skill to automatically emit Role.xml, Ext/Rights.xml, and update Configuration.xml.

Can I automate rights assignment for catalogs and documents in 1C configurations?

Yes, you can automate rights assignment across catalogs, documents, and registers by defining object rights and presets in JSON, which generates the required 1C metadata files.

Does this approach support RLS definitions when creating 1C role metadata?

Yes, generating 1C role metadata from JSON DSL supports optional RLS definitions, allowing you to apply record-level security filters alongside standard object rights and presets.

What is the best way to update Configuration.xml when adding new 1C roles?

The best way to update Configuration.xml when adding new roles is using a JSON DSL compiler, which automatically registers newly generated role metadata directly into the configuration file.

How do I validate rights when converting JSON to 1C permissions?

Validating rights when converting JSON to 1C permissions is handled automatically by the skill, which checks your JSON DSL definitions for consistency before generating the XML metadata files.

Do I need to manually edit Rights.xml when updating 1C roles?

No, you do not need to manually edit Rights.xml; the skill generates and updates Ext/Rights.xml automatically from your JSON DSL definitions, applying nested objects and presets.