xpz-builder

Generate GeneXus XPZ/XML envelopes via conservative template cloning.

11|3|Updated Mar 26, 2026

Search Tags:#packaging #xml #risk #cloning #envelope #genexus #xpz

Ready to run

npx skills add https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills --skill xpz-builder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: xpz-builder
Source: https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills/tree/main/xpz-builder
Command: npx skills add https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills --skill xpz-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates GeneXus XML objects for XPZ packaging using conservative cloning from empirical templates. Applies risk rules, validates structure, and serializes the correct XPZ envelope. Does not affirm import or build success — that requires external IDE validation.

Core Features & Use Cases

Conservative cloning based on comparable templates
Risk assessment and envelope serialization according to XPZ rules
Validation of structure and GUIDs; requires IDE confirmation for import/build

Quick Start

Generate an XPZ/XML envelope for a target GeneXus object using the most comparable template.

Frequently Asked Questions about xpz-builder

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

FAQPage Schema

How do I generate a GeneXus XPZ package from an XML object?▼

GeneXus XPZ packaging is automated by conservatively cloning objects from empirical templates, applying risk validation, and serializing the correct XPZ envelope for the target XML artifacts.

What is the safest way to clone GeneXus objects for XPZ export?▼

The safest way to clone GeneXus objects is through conservative cloning based on comparable templates, which includes strict envelope rule validation, structural integrity checks, and GUID validation before export.

Do I need to validate XPZ imports in the GeneXus IDE after generating the XML?▼

Yes, you need external GeneXus IDE validation to confirm import or build success, because generating the XPZ envelope and validating GUIDs does not affirm that the import will succeed without IDE confirmation.

Can I use this approach to clone objects across different XPZ projects?▼

Yes, conservative cloning and envelope serialization workflows are designed to apply across XPZ projects, allowing you to package and clone objects while maintaining structural integrity and enforcing risk validation.

Why does my generated XPZ envelope fail the import risk checks?▼

XPZ envelope imports may fail if risk validation rules are not met, or if structural integrity and GUID validation checks identify mismatches between the cloned object and the comparable empirical template.