evaluate-generated-service

Evaluate semantic correctness and deployment readiness of a service from a .dtrx application.

2|Updated Feb 13, 2026

Search Tags:#code generation #deployment readiness #semantic verification #service evaluation #DSL analysis

Ready to run

npx skills add https://github.com/keturk/datrix --skill evaluate-generated-service

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evaluate-generated-service
Source: https://github.com/keturk/datrix/tree/main/claude-config/.claude/skills/evaluate-generated-service
Command: npx skills add https://github.com/keturk/datrix --skill evaluate-generated-service

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive evaluation of a single service from a .dtrx application, ensuring the semantic correctness of the DSL source and the deployment readiness of the generated output.

Core Features & Use Cases

Semantic Verification: Full semantic verification of the DSL source against the generated output.
Completeness Checking: Checks for the completeness of generated artifacts.
Deployment Assessment: Determines if the service can be deployed and run.
Service Name Evaluation: Evaluates a specific service from a large project.
Service Generation Issue Debugging: Helps debug specific service generation issues.
Verifying Semantic Correctness: Verifies the semantic correctness of transpiled code for one service.

Quick Start

Use the /evaluate-generated-service skill to evaluate the 'product-service' service by providing the source .dtrx file and the generated service directory path.

Frequently Asked Questions about evaluate-generated-service

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

FAQPage Schema

How do I verify semantic correctness of generated service code from a DSL source?▼

You can verify semantic correctness by evaluating the service's .dtrx file against its generated output directory. This performs deep analysis to ensure the transpiled code accurately reflects the original DSL semantics and checks for deployment readiness.

What is the best way to check deployment readiness for a generated service?▼

Checking deployment readiness involves assessing the completeness of generated artifacts from the .dtrx application. This evaluation determines if the transpiled service output is complete and fully ready to be deployed and run.

How do I debug issues with generated service code from a .dtrx application?▼

To debug generated service code issues from a .dtrx application, perform deep analysis on the specific service. This helps identify semantic mismatches and completeness errors by comparing the DSL source directly with the transpiled output.

Can I evaluate just one service from a larger generated .dtrx project?▼

Yes, you can evaluate a single service from a larger generated .dtrx project. By providing the source .dtrx file and the specific generated service directory path, the evaluation focuses entirely on that individual service's semantic correctness.

Why does my generated service output not match the original DSL source semantics?▼

Generated service output might not match DSL source semantics due to transpilation errors or incomplete artifact generation. Performing a semantic verification and completeness check on the .dtrx output helps pinpoint where the generated code diverges from the intended logic.