subsystem-info

Analyzes 1C:Enterprise subsystem structure from XML configuration dumps including content, children, and command interface.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill subsystem-info-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subsystem-info
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/subsystem-info
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill subsystem-info-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Navigating a large 1C:Enterprise configuration to understand what a subsystem contains, where it sits in the hierarchy, and how its command interface is configured requires manually reading many XML files. This Skill reads the subsystem XML from a configuration dump and returns a compact, typed description of the structure. ## Core Features & Use Cases - Subsystem composition: Returns full object names in content, objects grouped by type in groups, and child subsystem names in children. - Hierarchy trees: A Subsystems directory returns the full registered tree; a registered subsystem XML returns a focused tree with the ancestor chain from the root plus all descendants. - Command interface and support status: Exposes includeInCommandInterface, useOneCommand, commandInterface placement data, and the support field from Ext/ParentConfigurations.bin as a guardrail before editing. - Use Case: Before running unica.subsystem.edit on the Sales subsystem, call this Skill to check its support status, review its current content, and see exactly where it sits in the configuration tree. ## Quick Start Ask the assistant to show the structure and command interface of the subsystem at src/Subsystems/Продажи.xml using the subsystem-info skill.

Frequently Asked Questions about subsystem-info

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

FAQPage Schema
How do I inspect the structure of a 1C:Enterprise subsystem?▼

Call the unica.subsystem.info MCP tool with the SubsystemPath pointing to the subsystem XML file in your configuration dump. It returns the subsystem's content, groups by object type, children, and command interface settings.

How to get the full subsystem tree of a 1C configuration?▼

Pass the Subsystems directory path as SubsystemPath instead of a single XML file. The result contains a tree of root subsystems with content counts and nested children built from Configuration/ChildObjects and recursive Subsystem/ChildObjects.

Can I select a subsystem by logical metadata address instead of file path?▼

Yes, pass sourceSet with a metadataPath like Subsystem.<Name> instead of SubsystemPath. Exactly one selector is allowed; providing both is rejected with a selector_conflict error.

Why does subsystem info return provider_unavailable?▼

The tool returns provider_unavailable when the registered descriptor is missing, corrupted, a symbolic link, or lacks a single canonical IncludeInCommandInterface. It refuses to return a partial tree instead of unproven data.

What does a null commandInterface mean for a 1C subsystem?▼

A null commandInterface means the subsystem has no CommandInterface.xml file at all. This differs from an interface that exists but hides nothing, so treat null as absence of the file rather than default visibility.