cf-info

Analyzes 1C:Enterprise configuration structure from Configuration.xml dump files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with 1C:Enterprise configurations, developers need a quick overview of what a configuration contains — its properties, object composition, and support status — without manually parsing large XML dump files. This Skill reads Configuration.xml and returns typed, structured data instead of raw text reports. ## Core Features & Use Cases - Configuration identity and properties: Returns name, synonym, version, vendor, compatibility mode, launch mode, and other root properties from the dump. - Object composition counters: Provides per-kind object counts via childObjects plus a totalObjects total, so you can see how many catalogs, documents, or registers exist. - Support status inspection: Reads Ext/ParentConfigurations.bin to report whether the configuration is supported, an extension, or removed from support, with locked/editable/removed object counters — a risk signal before mutating operations. - Use Case: Before modifying a configuration, call the tool with the dump directory to check data.support.state and confirm how many objects are locked, then review childObjects to understand the configuration's composition. ## Quick Start Ask the assistant to show the structure and support status of the 1C configuration located in the src dump directory.

Frequently Asked Questions about cf-info

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

FAQPage Schema
How do I get an overview of a 1C configuration structure?▼

Call the unica.cf.info MCP tool with ConfigPath pointing to Configuration.xml or its dump directory. It returns typed data with identity, properties, per-kind object counts, and total object count, so no manual XML parsing is needed.

How to check 1C configuration support status before editing?▼

Read the data.support field returned by unica.cf.info. Its state value distinguishes supported, extension, notSupported, and removed configurations, while the objects counters show how many objects are locked, editable, or removed.

Can I pass a directory instead of Configuration.xml path?▼

Yes, ConfigPath accepts either the Configuration.xml file or the dump directory containing it; the tool locates the file itself. Alternatively, pass a sourceSet name from v8project.yaml, but never both selectors at once.

Why do I get a selector_conflict error with unica.cf.info?▼

The selector_conflict error occurs when both sourceSet and ConfigPath are provided in the same call. Per ADR-0049, exactly one target selector is allowed, so remove one of the two parameters and retry.

What object counts does the 1C configuration analysis return?▼

The data.childObjects field returns an array of kind/count pairs for each metadata object type in the configuration, and data.totalObjects gives the overall total. Counts are read from the array directly rather than parsed from report text.