epf-init

Generate a 1C:Enterprise External Data Processor XML scaffold with object module.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill epf-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-init
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/source/epf-init
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill epf-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create a ready-to-edit External Data Processor scaffold for 1C:Enterprise by generating the initial XML metadata and the object module, providing a solid starting point for EPF development.

Core Features & Use Cases

  • Generates a root <Name>.xml with ExternalDataProcessor metadata and a basic Ext/ObjectModule scaffold.
  • Creates a standard Ext/ ObjectModule.bsl with placeholder regions to enable immediate editing.
  • Ensures deterministic output, including a fixed ClassId and UTF-8 with BOM encoding, aligned with the typical 1C EPF workflow.

Quick Start

Run epf-init with <Name> and optional <Synonym> to create a new EPF scaffold under 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 new External Data Processor for 1C:Enterprise development?

To scaffold a new External Data Processor for 1C:Enterprise, run the initialization tool with a Name and optional Synonym to generate the root XML metadata and object module under the src directory.

What files are generated when creating a 1C EPF scaffold?

Creating a 1C EPF scaffold generates a root <Name>.xml file containing ExternalDataProcessor metadata and a standard Ext/ObjectModule.bsl file with placeholder regions for immediate editing.

Does the generated 1C External Data Processor XML include a fixed ClassId and specific encoding?

Yes, the generated 1C External Data Processor XML includes a deterministic fixed ClassId and uses UTF-8 encoding with BOM to align with standard 1C EPF workflow requirements.

Can I use this scaffolding tool for Cursor-based 1C development workflows?

Yes, you can use this scaffolding tool for Cursor-based 1C development workflows to produce a consistent directory structure and ready-to-edit External Data Processor files.

What parameters do I need to start a 1C EPF initialization?

To start a 1C EPF initialization you need to provide the Name parameter, while the Synonym and SrcDir parameters are optional for customizing the generated metadata and output path.

Why does my 1C External Data Processor require UTF-8 with BOM encoding for the XML metadata?

1C External Data Processor XML metadata requires UTF-8 with BOM encoding to ensure deterministic file creation and proper recognition by the 1C:Enterprise platform during loading.