role-validate

Validate 1C role Rights.xml structure and registration entries.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill role-validate-mmmmmm786mngb-jpg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-validate
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/role-validate
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill role-validate-mmmmmm786mngb-jpg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

1C role definitions frequently harbor errors after creation or modification, leading to misconfigured access rights and metadata. This Skill validates the Rights.xml structure, ensures XML well-formedness and correct namespaces, and checks basic role metadata and registration consistency.

Core Features & Use Cases

  • Validates Rights.xml structure (root element, namespace, and global flags).
  • Checks each role object for proper name, rights, nested vs non-nested objects, and RLS templates.
  • Verifies optional metadata when a metadata file exists (UUID, Name, Synonym).
  • Confirms Role registration in Configuration.xml to ensure deployment readiness.
  • Suitable for pre-commit checks, CI pipelines, and manual audits during role development.

Quick Start

Run the role-validate script against the Rights.xml path to verify role integrity.

Frequently Asked Questions about role-validate

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

FAQPage Schema
How do I validate 1C role rights in Rights.xml?

To validate 1C role rights, this Skill checks the Rights.xml structure for XML well-formedness, correct namespaces, proper names, and accurate rights definitions. It detects invalid UUIDs, missing role names, and incorrect rights configurations.

What errors can Rights.xml validation detect in 1C roles?

Rights.xml validation detects invalid UUIDs, missing role names, incorrect rights, and missing registration entries in Configuration.xml. It also checks nested versus non-nested objects and RLS templates to ensure metadata consistency.

Can I use this validation tool for 1C roles in a CI pipeline?

Yes, this validation tool is suitable for pre-commit checks, CI pipelines, and manual audits during 1C role development. It verifies role registration in Configuration.xml to ensure deployment readiness across local and extended project structures.

Do I need lxml to parse and validate 1C Rights.xml files?

Yes, you need lxml installed for XML parsing to validate 1C Rights.xml files. This dependency enables the Skill to parse XML structures, verify metadata files, and confirm role registration entries in Configuration.xml.

What's the best way to verify 1C role registration in Configuration.xml?

The best way to verify 1C role registration is to run the validation script against the Rights.xml path. It confirms deployment readiness by checking Configuration.xml entries and validating optional metadata like UUID, Name, and Synonym when metadata files exist.

Why does my 1C role metadata validation fail after modifying Rights.xml?

1C role metadata validation fails after modification due to incorrect XML structure, invalid UUIDs, missing role names, or unregistered entries in Configuration.xml. The validation tool identifies these specific structural and metadata consistency errors.