skd-decompile

Decompile 1C Data Composition System Template.xml files into JSON DSL drafts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It converts 1C Data Composition System Template.xml reports into editable JSON drafts so you can scaffold a new report or structurally refactor an existing one without hand-editing the source XML.

Core Features & Use Cases

  • Decompiles supported schema structures into the skd-compile JSON DSL.
  • Emits warning markers for unsupported fragments so you can patch them manually instead of losing them silently.
  • Fails fast on unsupported constructs such as picture cells, value storage types, nested schemas, or non-report wrappers.
  • Best for report scaffolding from an existing template, analysis of complex 1C report layouts, and template-driven restructuring.

Quick Start

Run the skill on a Template.xml file to generate a JSON draft, then review the companion warnings note and replace any unsupported sentinel nodes before compiling it back.

Frequently Asked Questions about skd-decompile

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

FAQPage Schema
How do I convert a 1C Data Composition System Template.xml into an editable format?

To convert a 1C Data Composition System Template.xml, you can decompile it into a JSON DSL draft. This allows you to scaffold new reports or structurally refactor existing layouts without manually editing the source XML.

What happens to unsupported XML fragments when decompiling 1C report templates?

When decompiling 1C report templates, the tool emits warning markers for unsupported XML fragments. This ensures unsupported constructs are flagged for manual patching rather than being lost silently during the JSON conversion.

Can I use this decompiler for 1C templates containing picture cells or nested schemas?

No, the decompiler fails fast on unsupported 1C template constructs such as picture cells, value storage types, nested schemas, or non-report wrappers. It performs deterministic parsing and rejects invalid schema inputs immediately.

What is the best way to scaffold a new 1C report from an existing template layout?

The best way to scaffold a new 1C report is by decompiling an existing Template.xml into a JSON DSL draft. You can then analyze the structural layout, review generated warnings, and replace unsupported nodes before compiling it back.

Does the 1C template decompiler require any external dependencies to run?

No external dependencies are required to run the 1C template decompiler. It operates independently using its built-in scripts to perform deterministic parsing and fail-fast validation on your Template.xml files.

Why does my 1C Template.xml fail validation during JSON DSL conversion?

Your 1C Template.xml fails validation during JSON DSL conversion because the tool uses fail-fast validation for invalid schema inputs. It immediately rejects unsupported constructs or non-report wrappers to prevent generating invalid JSON drafts.