epf-init

Generate a 1C external data processor scaffold with XML metadata and source files.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill epf-init-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-init
Source: https://github.com/msrv-tech/skills/tree/main/epf-init
Command: npx skills add https://github.com/msrv-tech/skills --skill epf-init-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Creating new 1C external data processors (EPF) from a clean scaffold to jump-start development with minimal boilerplate.

Core Features & Use Cases

  • Generates a ready-to-use EPF scaffold by emitting a root XML metadata file (Name.xml) and an Ext/ObjectModule.bsl inside a named directory.
  • Applies sensible defaults (Synonym defaults to Name, SrcDir defaults to src) and supports custom Name, Synonym, and SrcDir.
  • Useful for rapid prototyping or onboarding new 1C external data processors in a project.

Quick Start

Run the epf-init tool with -Name and optional -Synonym and -SrcDir to generate a new EPF scaffold.

Frequently Asked Questions about epf-init

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

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

To create a 1C external data processor scaffold, specify a Name and optional Synonym and SrcDir. The tool generates a root Name.xml metadata file and an Ext/ObjectModule.bsl module inside a structured src directory.

What is the minimal file structure needed for a new 1C EPF?

The minimal file structure for a 1C EPF includes a root Name.xml metadata file and an Ext/ObjectModule.bsl source file. These are placed under a named src/NAME directory to ensure a valid external data processor tree.

Can I set a custom synonym and source directory when generating 1C EPF metadata?

Yes, you can specify custom Synonym and SrcDir parameters when generating 1C EPF metadata. If omitted, the Synonym defaults to the provided Name, and the SrcDir defaults to src for the output structure.

What's the best way to reduce boilerplate when starting 1C external data processor development?

The best way to reduce boilerplate is to use an automated scaffolding tool that instantly generates the required XML metadata and minimal BSL source tree. This jump-starts development by providing a ready-to-use EPF structure.

Does generating an EPF scaffold require any external dependencies?

Generating an EPF scaffold requires no external dependencies. The tool operates standalone using internal scripts to write the XML metadata and BSL source files directly to your specified directory.