role-validate

Validate 1C role Rights.xml files for structure, permissions, and metadata.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill role-validate-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-validate
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/role-validate
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill role-validate-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

This Skill checks a 1C role’s permissions file for structural, semantic, and metadata errors before the role is used in a configuration, helping you catch broken access rules early.

Core Features & Use Cases

  • XML Validation: Verifies that Rights.xml is well-formed, uses the expected root element, and includes required global flags.
  • Rights Consistency Checks: Confirms that object rights match the allowed rights for 1C object types, including nested objects and service channels.
  • RLS and Template Review: Detects empty restriction conditions and validates restriction templates for completeness.
  • Metadata and Registration Checks: Optionally validates role UUID, name, synonym, and registration in Configuration.xml.
  • Use Case: After editing a role in a 1C configuration, run this Skill to quickly identify malformed XML, unsupported rights, or missing metadata before deployment.

Quick Start

Use the role-validate skill to inspect the specified 1C role folder or Rights.xml file and report any validation errors, warnings, and metadata issues.

Frequently Asked Questions about role-validate

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

FAQPage Schema
How do I validate a 1C role Rights.xml file for structural and permission errors?

To validate a 1C role Rights.xml file, parse the XML structure and check object rights against allowed permissions for 1C object types. This confirms well-formed XML, verifies required global flags, and detects empty RLS restriction conditions.

What does 1C role metadata validation include beyond the Rights.xml file?

1C role metadata validation includes checking the role UUID, name, and synonym for correctness. It also optionally verifies the role's registration entry within the Configuration.xml file to ensure full configuration consistency before deployment.

How do I check for empty RLS restriction templates in a 1C configuration?

To check for empty RLS restriction templates in a 1C configuration, parse the Rights.xml file and validate restriction templates for completeness. This detects empty restriction conditions that could compromise access control rules.

Can I use lxml to verify 1C role rights and access control configurations?

Yes, you can use lxml to verify 1C role rights and access control configurations. The library provides the XML parsing capabilities required to inspect Rights.xml, validate structural correctness, and apply rights-type rules.

When should I run a 1C role rights validation check?

You should run a 1C role rights validation check after editing a role in a 1C configuration. This helps quickly identify malformed XML, unsupported rights, or missing metadata before deployment, catching broken access rules early.