Skip to content

mindbox-cloud/agent-skills / plugins/mindbox/skills/flow-create

flow-create

Verified

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 when: the flow already exists and only needs describing or checking — this skill builds, it does not report; the request is to launch, stop or delete something, which stays a human decision.

references/mechanics.md

View on GitHub
# Following a documented mechanic

Read this when the person names a marketing job instead of describing the blocks they want.

## What the reference owns, and what you own

The wiki's mechanics sub-folder owns **the assembly**; you own the **behaviour** — deciding a match,
asking the mechanic's decisions, building under the write path, and reporting where you departed.

## Deciding whether one matches

1. **Read the sub-folder's index first.** It is the only thing that says which mechanics exist. A
   mechanic you remember and cannot find there does not exist for this purpose.
2. **Read a candidate in the order the folder states**; the recognition document decides the match,
   never the name.
3. **Match on what the mechanic says it is for, against what the person actually asked for.** A word
   in common is not a match. Where it plainly covers the request, it — not your own arrangement of
   blocks — is the design.
4. **A partial match is not a licence to stretch it.** Take only what it covers, tell the user which
   part of their request it covers and which it does not, and treat the remainder as an ordinary
   request: described by them, built from their description. **A check the mechanic requires that
   cannot be built is a blocking decision for the user** — drop the check, replace it with one they
   name, or drop that block — and never a departure you take on your own and record at hand-over
   (`references/filter-delegation.md` → *A clause that cannot be expressed*).
5. **If nothing matches, say so** and build only what they describe (step 3) — that is not a failure.

**A preset named after a mechanic is not that mechanic** (`references/creation.md` → *Starting from a
preset*).

**Never improvise a mechanic the folder lacks, and never fill a hole in one it carries:** that is a
documentation gap to report (CRITICAL 2).

## The decisions come before the first write

A documented mechanic states what must be settled before anything is built, and the folder is where
that list lives. **Read it at that point — before your first write — and ask it in the step-3
batch.** Not after the first block, and not discovered while filling one: what those answers settle
is not what a later write can revise, so an answer arriving late costs a rebuild.

Ask them in the folder's own words, in the same batch as everything else.

Where the folder states what to do with a question that goes unanswered, follow it — and **say at
hand-over that you did**. An assumption the reference licenses is still an assumption the user has
not seen.

## Building it

- The mechanic decides **the shape**; the write path and the `## CRITICAL` rules decide **how a block
  is written**, and they win on writing.
- **Filters are still not yours.** A mechanic saying what a condition is *about* is not a filter
  body; delegate it like any other (`references/filter-delegation.md`).
- **Entities are still resolved from names, by you** (step 2). A mechanic naming the *kind* of thing
  a block points at never supplies an id, and no mechanic makes one guessable.
- **Verify every block regardless** (step 6). A mechanic that matched perfectly is no reason to
  trust a write.

## The rules that hold across mechanics

`mechanics.best_practices` binds every flow you build, matched mechanic or not; read it while you are
in the folder and design against it, and where the request forces a departure, say so at hand-over.

## At hand-over

Name the mechanic you followed, and **every place your build departs from it** — a branch left out,
a question that went unanswered and what you assumed instead, a part of the request it did not
cover. Ranked with the rest of what is missing (step 8, `references/hand-over.md`). A design the
user cannot compare against its reference is one they have to re-derive from the graph.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall