cfe-init

Creates 1C:Enterprise configuration extension XML source scaffolds via the unica MCP tool.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a new 1C:Enterprise configuration extension (CFE) requires manually creating correctly structured XML source files, matching compatibility modes, and language UUIDs from the base configuration. This Skill automates that scaffolding so the extension is valid from the start. ## Core Features & Use Cases - Extension Scaffolding: Generates Configuration.xml, Languages/Русский.xml, and optionally Roles/ for a new extension. - Auto-Detection from Base Configuration: Reads v8project.yaml or a provided ConfigPath to derive CompatibilityMode and the language UUID automatically. - Purpose-Aware Setup: Supports Patch, Customization, and AddOn purposes with configurable name prefix, version, vendor, and compatibility mode. - Use Case: You need a patch extension for an ERP 8.3.24 infobase. Point the Skill at the base configuration dump and it creates the extension scaffold with the correct compatibility mode and language UUID, then verifies it with unica.cfe.validate. ## Quick Start Ask the assistant to create a new 1C configuration extension named MyExtension using the base configuration dump at your source path, with dry run disabled once you confirm the change.

Frequently Asked Questions about cfe-init

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

FAQPage Schema
How do I create a 1C configuration extension from scratch?▼

Provide the extension name and optionally the path to the base configuration dump. The Skill calls the unica.cfe.init MCP tool to generate Configuration.xml, the Russian language file, and optionally a Roles folder with correct structure.

How to set compatibility mode for a 1C extension automatically?▼

Pass the ConfigPath parameter pointing to the base configuration dump, or keep a v8project.yaml with a CONFIGURATION source-set in the workspace. The Skill reads the dump and derives CompatibilityMode and the language UUID automatically.

What is the difference between Patch, Customization, and AddOn extension purposes?▼

Patch is for fixing bugs in the base configuration, Customization is for adapting behavior, and AddOn adds new functionality. The Purpose parameter defaults to Customization and is written into the generated extension metadata.

What happens if no base configuration path is provided?▼

The extension is still created but with a warning: the language UUID is set to zeros and CompatibilityMode falls back to the default Version8_3_24. You can supply ConfigPath later or accept the defaults.

Does the Skill modify files without confirmation?▼

No. Mutating calls default to dry run mode. The dryRun parameter is set to false only when the user explicitly requests the change, so you can preview the scaffold before anything is written.