epf-init

Generate a minimal 1C external processing scaffold with metadata XML and module stub.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill epf-init-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-init
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/epf-init
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill epf-init-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When you need to create a new external processing (EPF) in 1C, writing the initial metadata XML and required module stub is repetitive and error-prone.

Core Features & Use Cases

  • Creates a minimal EPF scaffold: generates the root metadata XML file for an ExternalDataProcessor and a dedicated processing folder.
  • Builds the module stub: creates Ext/ObjectModule.bsl with UTF-8 BOM and a minimal set of empty sections.
  • Supports Cyrillic safely: allows passing Name/Synonym in Base64 to avoid Windows PowerShell child-process Cyrillic issues.
  • Use case: you start a brand-new external data processor for integration (e.g., exporting data or calling services) and want the correct base structure to begin implementation immediately.

Quick Start

Give the AI the command: /epf-init МояОбработка Моя обработка.

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 new 1C external processing project structure?

Scaffolding a 1C external processing project requires generating the root metadata XML and an Ext/ObjectModule.bsl stub. This script provisions the initial file structure for forms, UI, and BSL implementation work.

What is the minimal file structure needed to start 1C EPF development?

The minimal 1C EPF file structure requires a root metadata XML file for an ExternalDataProcessor and a dedicated processing folder containing the Ext/ObjectModule.bsl stub.

How do I pass Cyrillic characters when generating 1C EPF metadata in PowerShell?

To pass Cyrillic characters when generating 1C EPF metadata in PowerShell, provide the Name and Synonym parameters as Base64-encoded strings to avoid child-process encoding issues.

Does the 1C external processing scaffold overwrite existing BSL module files?

No, the 1C external processing scaffold does not overwrite existing files. It safely writes the UTF-8 (with BOM) metadata XML and module stubs into the target SrcDir without replacing current content.

Why does my 1C ExternalDataProcessor module require UTF-8 BOM encoding?

Your 1C ExternalDataProcessor module requires UTF-8 BOM encoding for proper Cyrillic and metadata parsing. The scaffold script enforces this encoding when creating the ObjectModule.bsl stub.