makedsl

Generates Make platform DSL YAML defining apps, entities, fields, and relations.

5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/qfeius/make-platform-skills --skill makedsl-qfeius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makedsl
Source: https://github.com/qfeius/make-platform-skills/tree/main/skills/makedsl
Command: npx skills add https://github.com/qfeius/make-platform-skills --skill makedsl-qfeius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing data models on the Make platform requires writing precise DSL YAML for apps, entities, fields, and relations, with strict key constraints, field-type capabilities, and relation cardinality rules that are easy to get wrong by hand. ## Core Features & Use Cases - DSL Schema Generation: Produces valid Make.App, Make.Entity, Make.Field, and Make.Relation YAML covering text, number, select, user, department, file, date, and Lookup field types. - Data API Guidance: Provides CRUD-LS request contracts, filter.expression CEL syntax, relation writes via qfei_relation, and file upload flows from bundled reference docs. - Use Case: Ask to model a project management app, and receive complete YAML for the project and task entities, a one-to-many relation, Lookup fields, and the corresponding Data API request bodies ready for makecli apply. ## Quick Start Ask the assistant to design a Make platform DSL model for a project management app with project and task entities, including fields, relations, and sample Data API calls.

Frequently Asked Questions about makedsl

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

FAQPage Schema
How do I define entities and fields in Make platform DSL?

Define a Make.Entity YAML with a unique key, display name, appKey, and a properties.fields list of Make.Field entries. Each field specifies a type such as Make.Field.Text, Number, SingleSelect, or File, plus optional properties and validations.

How do I model relations between entities in Make DSL?

Declare a Make.Relation with from and to entity keys and cardinality of one or many. The platform chooses FK or join-table storage automatically, and you expose related data through Lookup fields referencing the relationKey.

What field types does the Make platform DSL support?

Supported types include ID, Text, TextArea, Number, Currency, Percent, Date, DateTime, DateRange, SingleSelect, MultiSelect, URL, File, SingleUser, MultiUser, SingleDepartment, MultiDepartment, and the derived Lookup field.

How do I filter records with the Make Data API?

Pass a filter object containing an expression string with CEL syntax to MakeService.ListResources, for example status in ['todo','doing'] or name.contains('x'). Only field keys are allowed, and nested OR inside AND groups is unsupported.

When should I use a Lookup field instead of a relation ID field?

Use a Lookup field whenever one entity must display another entity's field data; custom relation ID fields are forbidden. Lookup only displays and filters data, while actual relation writes go through data.qfei_relation in create or update calls.

Does makedsl deploy the generated YAML to the Make platform?

No, it only designs and generates the DSL YAML. Deployment is handled separately with makecli apply, and published services should load schema from Meta APIs rather than hard-coded local DSL files.