maestra-io/maestra

Build a CDP filter (a selection of customers, products or actions; the basis of a segment) from a natural-language request: the filters-domain reference → draft → validation → resolving the project's catalogue wording → a link to the list in the project, and the filter itself on request. Triggers: "build a filter", "make a segment", "select customers who", "who bought X in the last N days", "filter by products", "starter filters". NOT for: datamart analytics — "count", "how many", a report, a metric, ClickHouse SQL (the analytics_* tools of the same MCP server); explaining a filter that already exists (/maestra:filter-explain).

Explain an existing CDP filter in plain words: what selection it describes, which conditions it holds, and what about it cannot be read. Takes the filter as the project stores it — the JSON. Triggers: "explain this filter", "what does this filter do", "what does this segment select", "who does this selection pick". NOT for: building a new filter or changing one (/maestra:filter-build); datamart analytics — "count", "how many", a report, a metric (the analytics_* tools of the same MCP server).

Creates and modifies emails for the Maestra editor (visual builder) from a text description. Use when the user asks to create or modify an email, or describes an email template. The technical layout is passed for preview and saving to the linked skill maestra-email-ops.

Operational actions for Maestra emails — preview, reading and saving the visual template, reading/editing campaign metadata, searching gallery assets via MCP, uploading attached/local images via MCP upload link, PNG preview. Use together with the maestra-email generator when you need images, preview, validation, or writes to Maestra.