nexa

Analyze GeneXus Knowledge Base prompts and generate execution plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/genexuslabs/genexus-skills --skill nexa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexa
Source: https://github.com/genexuslabs/genexus-skills/tree/main/nexa
Command: npx skills add https://github.com/genexuslabs/genexus-skills --skill nexa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a focused, self-contained workflow to interpret user intents related to GeneXus Knowledge Base objects, validate feasibility against repository constraints, and generate actionable execution plans with required references.

Core Features & Use Cases

  • Interpret user intents for Knowledge Base objects (Transactions, Data Providers, Data Selectors, SDTs) and verify feasibility against the repository structure.
  • Generate concise execution plans with concrete steps, required references, and artifact locations, ready for user approval.
  • Load and reuse only the necessary references from references/ and shared common-* dependencies to minimize context and ensure deterministic planning.

Quick Start

Describe a KB task such as creating a new Transaction or reviewing a Domain, and the skill will return an actionable plan and the required references.

Frequently Asked Questions about nexa

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

FAQPage Schema
How do I plan modifications for GeneXus Knowledge Base objects before making changes?

To plan GeneXus Knowledge Base object modifications, analyze user prompts to determine a precise execution plan, identify necessary artifacts like Transactions and Domains, and locate their repository paths to prepare reuse before any changes are made.

What is the best way to identify required references for a GeneXus Transaction task?

Identifying required references for a GeneXus Transaction involves loading necessary repository paths from the references directory and shared dependencies to minimize context and ensure deterministic planning.

How do I validate feasibility against repository constraints for GeneXus Data Providers?

Validating feasibility for GeneXus Data Providers requires interpreting user intents and verifying them against the existing repository structure to ensure requested artifacts and locations are available.

Can I generate an execution plan for GeneXus Data Selectors and SDTs without modifying the Knowledge Base?

Yes, you can generate a concise execution plan with concrete steps, required references, and artifact locations for GeneXus Data Selectors and SDTs ready for user approval without modifying the Knowledge Base.

Do I need to specify module placements when planning GeneXus object modeling tasks?

Specifying module placements is part of the structured execution plan, which details required references, module placements, and activation steps to ensure proper artifact organization before changes are made.