generate-execdsl

Transform business rules into ExecDSL-compliant JSON DSL with validation.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/SukiEva/CheckEngine --skill generate-execdsl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-execdsl
Source: https://github.com/SukiEva/CheckEngine/tree/main/.codex/skills/generate-execdsl
Command: npx skills add https://github.com/SukiEva/CheckEngine --skill generate-execdsl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill converts business rules into a JSON DSL that complies with the current ExecDSL implementation constraints, and uses the repository's built-in validation script to perform post-generation checks and repairs. It helps generate the variables, steps, and on_fail structure from natural language prompts, validation rules, and SQL check requirements, and to verify that candidate DSLs satisfy the repository's check_engine parsing, references, message templates, and SQL safety rules.

Core Features & Use Cases

  • Automates the transformation of business rules into a top-level DSL structure consisting of variables, steps, and on_fail.
  • Aligns generated DSL with hard rules and intake checklist, and validates against the project-level validator, repairing issues within up to three iterations.
  • Determines DSL suitability for repository check_engine parsing, references, and messaging templates, ensuring safe SQL usage and proper outputs/consumes where relevant.

Quick Start

Provide your business requirements in natural language and run the generator to produce and validate the ExecDSL JSON until it passes project checks.

Frequently Asked Questions about generate-execdsl

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

FAQPage Schema
How do I convert business rules into a JSON DSL?

You provide natural language prompts, validation rules, and SQL check requirements to generate a JSON DSL. The system transforms these inputs into an ExecDSL-compliant structure containing variables, steps, and on_fail configurations.

What is the best way to validate generated DSL against repository check_engine parsing?

To validate generated DSL against repository check_engine parsing, use the built-in validation script. It checks references, message templates, and SQL safety rules, automatically repairing issues through up to three iterative fix cycles.

Can I use natural language to generate variables and steps for ExecDSL?

Yes, you can use natural language prompts to generate variables and steps for ExecDSL. The system interprets your input to automatically build the top-level DSL structure and aligns it with required validation rules and safe SQL usage.

How does the validation process handle SQL safety rules and message templates?

The validation process handles SQL safety rules and message templates by verifying candidate DSLs against the repository's built-in validator. It ensures proper outputs and consumes structures, applying iterative fixes when constraints are not met.

What are the limitations of automated DSL generation and validation?

A key limitation of automated DSL generation is the maximum of three iterative validation cycles. If the candidate DSL still fails repository check_engine parsing, reference checks, or SQL safety rules after three repair attempts, manual intervention is required.