epf-init

Generate XML metadata and BSL module scaffold for 1C external data processors.

511|99|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Nikolay-Shirokov/cc-1c-skills --skill epf-init-nikolay-shirokov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-init
Source: https://github.com/Nikolay-Shirokov/cc-1c-skills/tree/main/.claude/skills/epf-init
Command: npx skills add https://github.com/Nikolay-Shirokov/cc-1c-skills --skill epf-init-nikolay-shirokov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of the basic file structure and initial code for a new 1C external data processor, saving developers time on repetitive setup tasks.

Core Features & Use Cases

  • Generates XML Metadata: Creates the root XML file for an external data processor with essential UUIDs and properties.
  • Initializes Object Module: Sets up a basic BSL (1C's scripting language) module with predefined regions.
  • Use Case: When starting a new 1C development task that requires an external data processor, use this Skill to quickly generate the foundational files, allowing you to focus immediately on writing the core logic.

Quick Start

Use the epf-init skill to create a new external data processor named 'MyNewProcessor' with the synonym 'МояНоваяОбработка' in the 'src' directory.

Frequently Asked Questions about epf-init

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

FAQPage Schema
How do I scaffold a 1C external data processor?

To scaffold a 1C external data processor, you need to generate a root XML metadata file and an initial object module. This provides the foundational UUIDs, properties, and predefined BSL regions for your project.

What files are generated when creating a 1C external data processor?

Creating a 1C external data processor generates a root XML metadata file containing essential UUIDs and properties, alongside an initial BSL object module structured with predefined regions for your code.

Can I specify a custom name and directory when scaffolding 1C external data processors?

Yes, you can specify custom names for the external data processor and its synonym, as well as define the target source directory. This allows flexible project bootstrapping for 1C development.

What is the best way to bootstrap a new 1C external data processor project?

The best way to bootstrap a 1C external data processor project is to automate the creation of the basic file structure and initial BSL code. This eliminates repetitive setup tasks and lets you focus on core logic.

Does scaffolding an external data processor include predefined BSL module regions?

Yes, scaffolding an external data processor initializes a basic BSL object module that includes predefined regions. This sets up the necessary code structure immediately during project generation.