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/validation.md

View on GitHub
# Validating the flow version

Read at step 7, and again at 7b — the mailing edits reopen validation.

- [The call's own failure modes](#the-calls-own-failure-modes)
- [Sorting what it reports](#sorting-what-it-reports)
- [A change asked for after a validation that passed](#a-change-asked-for-after-a-validation-that-passed)

## The call's own failure modes

A refusal; an answer **naming nothing at all** (validation did not run); a stale-token claim handing
back the token you already hold. **None of them is about your flow, and none is a licence to loop.**
Never delete a block on suspicion — a deletion made on a guess costs you a block that was fine and
leaves the real cause in place. One row each in `references/troubleshooting.md` → *Validation*.

**A second call on a version that is *still* passing is a silent no-op**: it returns the same success
line and the same row version, with nothing to tell it from a fresh pass — so never offer a repeated
identical success as new evidence. After any further write, or on a version that came back with
problems, validating again is the step, and that call is a **real** validation: **any block operation
returns a passing version to in-development**, which is what reopens it.

**The call does not re-shape the version's blocks**, pass or fail — the reads you are holding stay
valid baselines, and only the row version moves (`SKILL.md` step 7).

## Sorting what it reports

Three kinds, and the difference decides whether you write anything at all.

1. **Expected gaps** — what you already knew you could not author: an id no tool reaches, a
   condition the flow's scope set cannot express. **Do not retry and do not invent them away.** Carry
   them to step 8 as what the flow still needs.
2. **Problems that are yours to fix** — a malformed block, a missing required member, a dead end you
   did not intend, an unconnected block. Fix it, verify in step 6 and validate again — the version
   did not pass, so this is not the no-op. **Take a pre-write read before the fixing write** (step 5).
   The loop runs inside CRITICAL 6: what means stop is the *same* objection returning unchanged.
3. **A problem that is yours and that you could not write** — a value you had to stop on under
   CRITICAL 2, or an objection naming a member no write reaches (`SKILL.md` → CRITICAL 6). Do
   not retry it and do not invent a value to silence it. Carry it to step 8 **ranked**: if it is the
   user's headline requirement, say plainly that the flow will not run until it is set, as a gap on
   your side.

**If you cannot tell which kind a message is, report it verbatim rather than guessing.** And **do not
assume a problem tells you where it is:** if it names no block, match it yourself from what you
wrote — but if **more than one** could be the subject, do not pick one. Report it verbatim, name the
candidates, and leave it to the user. Guessing is how you rewrite a block that was fine.

## A change asked for after a validation that passed

Re-read the flow for the current row version, and take step 5's full-detail read of every block you
will touch — the validation did not invalidate the reads you already hold. **Validating does
not by itself put the version out of reach**; which statuses accept writes is the write path's to
state. If a write *is* refused as not editable, say plainly that the change could not be applied to
this version, and stop.

If it goes through, **verify it in step 6 and validate again**: what stands behind the flow is the
validation after your last write.

# References

- `SKILL.md` → step 7 — the ordering rule and the ban on offering a pass as evidence
- `SKILL.md` → CRITICAL 6 — the session budget these failure modes run inside
- `references/troubleshooting.md` → *Validation* — one row per situation
- `references/hand-over.md` — where the three kinds end up
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: 197kUpdated 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: 197kUpdated 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: 197kUpdated Claude CodeCodexVerifiedInstall