1c-form-info

Parses exported 1C managed form Form.xml files into compact summaries of elements, attributes, commands, and events.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-form-info-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-form-info
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/1c-forms/info
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-form-info-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Exported 1C managed form files (Form.xml) can span tens of thousands of XML lines, making it impractical to understand a form's structure before modifying it in Configurator or creating elements programmatically in BSL. This Skill condenses that XML into a compact, readable summary. ## Core Features & Use Cases - Element Tree Summary: Renders the UI element hierarchy with type abbreviations, data bindings, visibility flags, and event handlers while skipping visual noise like tooltips and context menus. - Attributes, Parameters, and Commands: Lists typed form attributes (including ValueTable columns and DynamicList main tables), key parameters, and commands with handlers and shortcuts. - Pagination Protection: Limits output to 150 lines by default with -Offset and -Limit parameters for navigating very large forms. - Use Case: Before editing a document form in Configurator, run the script on its Form.xml to see the full element tree, attribute types, and event handlers in under 100 lines instead of reading 28,000 lines of raw XML. ## Quick Start Ask the assistant to run the 1c-form-info script against the exported Form.xml file of the form you want to inspect, providing the file path.

Frequently Asked Questions about 1c-form-info

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

FAQPage Schema
How do I view the structure of a 1C managed form without reading the full XML?

Run the form-info.ps1 PowerShell script with the -FormPath parameter pointing to the exported Form.xml file. It outputs a compact summary of the element tree, attributes, commands, and events, typically reducing tens of thousands of XML lines to under 150 lines.

How to analyze a large 1C Form.xml file that exceeds the output limit?

The script limits output to 150 lines by default and prints a TRUNCATED notice when exceeded. Use the -Offset parameter to continue from where output stopped, and -Limit to change the page size, for example -Offset 150 to view the next section.

Can this tool edit or generate 1C Form.xml files?

No, the skill is strictly read-only and only analyzes existing exported Form.xml files. Form changes must be made in 1C Configurator and exported to src/, or implemented through programmatic element creation in the form's BSL module.

What information does the form summary skip from the XML?

The script removes over 80 percent of XML volume, including visual properties like width, height, color, and font, auto-generated ExtendedTooltip and ContextMenu elements, multilingual wrappers, namespace declarations, and ID attributes. Use grep on element names for detailed inspection.

When should I inspect a 1C form structure before making changes?

Inspect before Configurator edits to find the correct group and element names, before BSL-created elements to identify stable runtime placement targets, and when navigating large unfamiliar forms to understand which attributes, commands, and handlers exist.