subsystem-info

Parse 1C subsystem XML exports to enumerate contents, child subsystems, and command interfaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyzes 1C subsystem structure from XML dumps to create a clear map of subsystems, contents, and command interfaces for easier navigation and configuration auditing.

Core Features & Use Cases

  • Parse Subsystem XML to enumerate contents, child subsystems, and CI presence, enabling quick audits of complex configurations.
  • Support modes overview, content, ci, tree, and full to tailor output for developers, testers, and administrators.
  • Use Case: You need to understand a large 1C configuration by listing its objects and relationships without manual XML digging.

Quick Start

Run the subsystem-info script with the path to your Subsystems/ directory or a single Subsystem XML to generate a structured report.

Frequently Asked Questions about subsystem-info

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

FAQPage Schema
How do I map 1C subsystem structures from XML exports?

To map 1C subsystem structures from XML exports, parse the Subsystem XML metadata to extract content items, child subsystems, and CommandInterface data, generating a structured overview for configuration navigation and auditing.

What is the best way to audit a large 1C configuration without manual XML digging?

The best way to audit a large 1C configuration is to run an automated parsing script on your Subsystems directory to enumerate contents and relationships, providing overviews, content lists, and CI details without manual XML digging.

Can I extract CommandInterface data across different modes from 1C Subsystem XML?

Yes, you can extract CommandInterface data across modes from 1C Subsystem XML by applying specific output modes like overview, content, ci, tree, and full to tailor the extracted configuration details for developers, testers, and administrators.

Does the 1C subsystem analysis script require lxml to parse XML?

Yes, the 1C subsystem analysis script requires the lxml dependency to parse XML exports, extract subsystem contents, and process MD Subsystem metadata for generating structured configuration reports.

What output modes are available for navigating 1C configuration subsystems?

Available output modes for navigating 1C configuration subsystems include overview, content, ci, tree, and full, allowing you to tailor the parsed XML reports for specific auditing and configuration navigation needs.