1c-platform-tools-external

Build and decompile 1C EPF/ERF external objects via extension commands or MCP tools.

178|16|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/yellow-hammer/vscode-1c-platform-tools --skill 1c-platform-tools-external
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-platform-tools-external
Source: https://github.com/yellow-hammer/vscode-1c-platform-tools/tree/main/resources/skills/1c-platform-tools-external
Command: npx skills add https://github.com/yellow-hammer/vscode-1c-platform-tools --skill 1c-platform-tools-external

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the build and decompilation of 1C external objects (EPF/ERF) via extension commands or MCP tools, helping to recover sources and manage caches efficiently.

Core Features & Use Cases

  • Build external processing and reports (EPF/ERF) from source code.
  • Decompile external objects back to readable source for inspection or modification.
  • Clear external file caches to ensure fresh, clean rebuilds in development workflows.
  • MCP integration maps commands to the corresponding MCP actions for streamlined automation.

Quick Start

Run the extension commands or MCP tools to build or decompile external objects, and clear the external cache when needed.

Frequently Asked Questions about 1c-platform-tools-external

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

FAQPage Schema
How do I build and decompile 1C external objects like EPF and ERF?

Build and decompile 1C external objects by running extension commands or MCP tools that convert source code to EPF/ERF files and back to readable source for inspection.

How do I clear external file caches for clean 1C rebuilds?

Clear external file caches by invoking the dedicated cache management command, which removes stale external processing data and ensures fresh EPF/ERF rebuilds during development.

Does building 1C external processing require a specific project path?

Building 1C external processing requires a projectPath to identify the root of the 1C project packagedef, defaulting to the workspace root if the path is not explicitly provided.

Can I automate 1C external object decompilation using MCP integration?

Automate 1C external object decompilation using MCP integration, which maps extension commands to corresponding MCP actions for streamlined, automated recovery of EPF and ERF sources.

What is the best way to recover readable source from compiled ERF files?

Recover readable source from compiled ERF files by decompiling the external objects through extension commands, transforming the binary reports back into modifiable source code.