role-info

Summarize 1C role rights from Rights.xml into a grouped audit report.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill role-info-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-info
Source: https://github.com/msrv-tech/skills/tree/main/role-info
Command: npx skills add https://github.com/msrv-tech/skills --skill role-info-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

1C role rights are stored in Rights.xml and need a compact, readable summary for audits. This Skill parses Rights.xml (and optional Role metadata) to produce a concise report of allowed rights, denied rights, and RLS indicators, saving time and reducing manual parsing errors.

Core Features & Use Cases

  • Grouped rights by object type (e.g., Catalog, Document) with clear indicators for allowed and optionally denied rights.
  • Detects and marks rights with RLS restrictions to highlight access controls in audits.
  • Includes role metadata (name and synonym) when available, and supports pagination for large roles.

Quick Start

Run role-info against a Rights.xml file to generate a compact rights summary.

Frequently Asked Questions about role-info

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

FAQPage Schema
How do I summarize 1C role rights from Rights.xml for an audit?

Summarizing 1C role rights involves parsing Rights.xml to produce a structured report grouping rights by object type, including Catalogs and Documents, while marking allowed, denied, and RLS-restricted access controls.

How can I detect RLS restrictions in a 1C Rights.xml file?

Detecting RLS restrictions in a 1C Rights.xml file requires parsing the role metadata to identify and tag rights configured with Row Level Security, highlighting them within the structured audit summary output.

Can I extract denied rights and role metadata from 1C configurations?

Extracting denied rights from 1C configurations is supported by parsing Rights.xml, which uses available role metadata to include role names and synonyms while optionally detailing denied rights in the output summary.

Does this rights analysis tool require lxml to parse 1C role files?

Parsing 1C role files requires the lxml dependency to analyze Rights.xml configurations, extracting role metadata and generating structured summaries grouped by object type with RLS indicators.

What is the best way to handle large 1C roles during rights auditing?

Handling large 1C roles during rights auditing is best managed using pagination support, which processes extensive Rights.xml files to systematically output structured summaries without manual parsing errors.