role-validate

Validate 1C role definitions in Rights.xml for structural correctness.

511|99|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Nikolay-Shirokov/cc-1c-skills --skill role-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-validate
Source: https://github.com/Nikolay-Shirokov/cc-1c-skills/tree/main/.claude/skills/role-validate
Command: npx skills add https://github.com/Nikolay-Shirokov/cc-1c-skills --skill role-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the structural integrity and correctness of 1C role definitions, preventing common errors and inconsistencies in access control configurations.

Core Features & Use Cases

  • XML Validation: Checks Rights.xml for well-formedness, correct namespaces, and valid elements.
  • Right and Object Type Checks: Verifies that rights assigned are appropriate for the object types and handles nested objects correctly.
  • Metadata Verification: Optionally validates role metadata like UUID, Name, and Synonym against the role's XML definition.
  • Use Case: After generating or modifying a role's Rights.xml file, use this Skill to automatically catch syntax errors, incorrect right assignments, or missing metadata before deploying it to a 1C system.

Quick Start

Validate the role definition located at 'Roles/MyRole/Ext/Rights.xml' and its metadata at 'Roles/MyRole.xml'.

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 before deployment?

To validate a 1C role Rights.xml file, parse the XML structure against predefined rules to check well-formedness, namespaces, and valid elements. This process catches syntax errors and incorrect right assignments in role definitions before system deployment.

What does 1C role structural validation check in access control configurations?

1C role structural validation checks the correctness of access control configurations by verifying XML format, rights, RLS, and metadata. It ensures assigned rights are appropriate for object types and handles nested objects correctly to prevent configuration inconsistencies.

Can I verify 1C role metadata like UUID and Synonym against the XML definition?

Yes, you can optionally verify 1C role metadata like UUID, Name, and Synonym against the role's XML definition. This metadata verification ensures the descriptive properties match the structural rights defined in the Rights.xml file.

Do I need PowerShell to check 1C role definitions for errors?

Yes, you need PowerShell to check 1C role definitions for errors. The validation process requires PowerShell to parse and analyze XML structures against predefined rules and object types for 1C:Enterprise 8.3 configurations.

Why does my 1C role Rights.xml fail after modification?

A modified 1C role Rights.xml may fail due to syntax errors, incorrect right assignments, or missing metadata. Validating the XML format, namespaces, and object type rights automatically catches these structural inconsistencies before deployment.

What's the best way to catch incorrect right assignments in 1C configurations?

The best way to catch incorrect right assignments in 1C configurations is to validate right and object type checks against predefined rules. This verifies that assigned rights are appropriate for the object types and handles nested objects correctly.