maestra-io/maestra
Maestra skills for marketers: emails in the visual editor (personalization, product rows, letter styles, recipients, test sends), segment filters — build one from a request in plain words, edit an existing one, explain what one selects — and marketing flows — summarize one, audit a project's flows for anti-patterns or for business results, and build a new flow from a plain-language request.
Build or edit a CDP filter — a selection of customers, products or actions, the basis of a segment — from a natural-language request, or change existing filter JSON. Returns a platform-confirmed filter and a link to the list in the project when available; does not save a segment. Russian triggers: "собери фильтр", "построй фильтр", "сделай выборку", "нужен сегмент", "выбери клиентов, которые...", "фильтр по товарам", "добавь условие в фильтр". English triggers: "build a filter", "make a segment", "select customers who...", "who bought X in the last N days", "filter products", "edit this filter", "add a filter condition", "starter filters". NOT for: explaining an existing filter (maestra:filter-explain); datamart analytics — "count", "how many", "сколько клиентов", a report, a metric, ClickHouse SQL (the analytics_* tools of the same MCP server).
Explain existing CDP filter JSON in plain language, including conditions and values that could not be read. Use when asked what a filter or segment selects. Does not change it. Russian triggers: "объясни фильтр", "что делает этот фильтр", "кого выбирает эта выборка", "разбери фильтр", "объясни условия сегмента". English triggers: "explain this filter", "what does this segment select", "who matches this filter", "explain these filter conditions". NOT for: building or editing a filter (maestra:filter-build); datamart analytics — "count", "how many", "сколько клиентов", a report, a metric (the analytics_* tools of the same MCP server).
Business audit of a project's marketing scenarios (flows), ending in fixes to them. First the figures: revenue, orders, funnel and rates per flow, over the period and against the month before and the year-earlier month, to find the flows with a problem and the ones that work best. Then, only for those, the construction: start block, conditions, sends, repeat settings, to name the block and the action that would fix it, or what to copy. Up to seven scenarios go through in full, the rest become hypotheses. Two report forms, chosen at the start: the full report, or a proposal deck with separate presenter notes. Use when the question is about business results, in any language: which flows earn and which do not, what the scenarios brought in for the month, one flow's money. Answers in the language asked. Read-only: don't use to audit one flow's structure with no figures (flow-issues-audit), to summarize what a flow does (flow-summary), or to create or edit anything.
Build a correct draft marketing scenario (flow) from a plain-language request: read the flows reference, resolve the entities the design needs to real ids, create and fill the blocks, wire the outputs, verify every block by reading it back, and hand over a link. Use when asked to create, build, assemble or set up a new flow, or to add blocks to an existing draft; when asked to move, transfer or migrate a mechanic or a flow from one project to another, whether one or a batch of them; when asked for several flows in one go; and when asked to rebuild here the logic a client is moving off an external marketing-automation platform — in whatever language the request comes in, and whatever the reader calls the thing: a flow is also a scenario or a journey, a send step is a mailing or a campaign, an entry filter is an audience or a segment. Don't use to describe or check an existing flow (maestra:flow-summary, maestra:flow-issues-audit), or to launch, stop or delete anything: that stays a human decision.
Technically audit a marketing scenario (flow): inspect its structure and flag known anti-patterns — processing-load and communication-correctness issues — each with a concrete fix and a short why. Use when asked to audit, review, health-check, or "find what's wrong / what to fix" in an existing flow, or across a whole project's flows. Don't use to summarize what a flow does (use flow-summary) or to create, edit, or launch a flow (use flow-create) — this skill is read-only.
Produce a concise, structured business summary of a marketing scenario (flow) from its structure. Use when you need to understand or explain what an existing flow does — before adapting it, editing it, auditing it, or reporting to a user, and on requests like "what does this flow do", "summarize the scenario" or "explain this flow". Reads the flow with the project's flow tools and looks up block / event / step meanings in the flows wiki. Don't use to audit a flow for problems (use flow-issues-audit) or to create, edit, or launch a flow (use flow-create); this skill is read-only.
Creates and edits emails for the Maestra email editor (visual builder) from a text description. Use when the user asks to create or change an email, describes an email template, or asks to make a campaign — including personalized content, product recommendation rows and letter styles. The technical layout is handed over for preview and saving through the companion skill maestra-email-ops.
Operational actions for Maestra emails — preview, reading and saving the visual template, letter styles, saved blocks, reading/editing campaign metadata and recipients (a segment or a filter), test sends, finding gallery assets via MCP, uploading images from the user's machine through the MCP App panel, PNG preview links, and an inbox-style mockup of the finished email (before/after when there is an earlier version) to share with a client or the team. Use together with the maestra-email skill when images, a preview, a check, a test send or a write to Maestra are needed, or when the user wants a picture of the email as it looks in an inbox ("before/after", "до/после", "mockup", "скриншот для клиента").