epf-validate

Validate 1C EPF and ERF metadata XML for structural errors.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill epf-validate-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-validate
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/epf-validate
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill epf-validate-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

This Skill checks 1C external processing and external report packages for structural correctness before they break in production, helping you catch XML, reference, and file layout issues early.

Core Features & Use Cases

  • Metadata validation: Verifies root metadata structure, internal info blocks, UUIDs, identifiers, and required properties.
  • Relationship checks: Confirms default forms, auxiliary forms, and report schemas point to real child objects.
  • Package integrity: Ensures forms and templates have both descriptor files and matching on-disk content.
  • Use case: Use it after generating or editing an EPF or ERF to confirm the package is complete and internally consistent before delivery.

Quick Start

Run the validator on your 1C external processing or report directory, or directly on its XML file, to verify structure, references, and required files.

Frequently Asked Questions about epf-validate

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

FAQPage Schema
How do I validate 1C EPF and ERF metadata XML before deployment?

You can validate 1C EPF and ERF metadata XML by parsing the package directory or XML file to check root metadata objects, internal info blocks, UUIDs, identifiers, and required properties for structural correctness before deployment.

What does 1C external processing package validation check for?

1C external processing package validation checks root metadata structures, internal info blocks, UUIDs, identifiers, required properties, cross-references to child objects, and consistent on-disk form or template file presence to ensure package integrity.

Can I use PowerShell to check 1C external report schemas and form references?

Yes, you can use PowerShell to check 1C external report schemas and form references by running validation scripts that confirm default forms, auxiliary forms, and report schemas point to real child objects within the XML metadata.

Do I need lxml to parse and validate 1C ERF and EPF files?

Yes, you need lxml for deterministic XML parsing when validating 1C ERF and EPF files, because the validation process requires consistent parsing of metadata structures, UUIDs, and cross-references.

Why does my 1C external report package fail validation after editing?

Your 1C external report package may fail validation after editing due to broken cross-references, missing on-disk form or template files, non-unique names, or incomplete metadata properties introduced during the editing process.