flowstate

Plugin flowstate from marketplace flowstate in picatz/flowstate. Commands read from the repo's manifest — 20 days ago.

Skills (6)

• flowfile-author

  Use when writing or changing a Flowstate Flowfile (workflow.yaml or *.flow.yaml); loops on the flow MCP tools until the file validates.

• flowfile-compose

  Use before adding a repeated expression, constant, shape, or block to a Flowstate Flowfile, or when a Flowfile repeats itself; picks vars, functions, types, a module (use:), or call:.

• flowfile-conventions

  Use while editing a Flowstate Flowfile; canonical spellings, secret references, and CEL pitfalls. Loads on its own when a Flowfile is open.

• flowfile-debug

  Use when a Flowstate run or test case misbehaves and you need to step through it, inspect values, or watch a durable run.

• flowfile-test

  Use when adding or running tests for a Flowstate Flowfile (*.test.yaml): stubbed tasks, scripted signals, virtual clock.

• flowstate-plugin-author

  Use when asked to write or change a Flowstate plugin (a task provider, the executable flowstate-plugin-<name>): decide if a plugin is needed, define the schema in Protobuf, test and rehearse it locally.

Slash commands (3)

• /flowstate:cel

  Try a CEL expression the way Flowstate evaluates it, then explain the result or the error

• /flowstate:debug

  Find why a Flowstate run or Flowfile failed and fix it

• /flowstate:new

  Start a new Flowstate workflow from a description

Subagents (2)

• flowfile-debugger

  Finds why a Flowstate run or Flowfile failed, reproduces it locally, and proposes the smallest fix to the Flowfile. Use for "why did this run fail" or a Flowfile that misbehaves.

• flowfile-engineer

  Writes, tests and debugs a Flowstate Flowfile end to end and reports evidence. Use for "make me a workflow that ...", for a failing Flowfile, or to harden one before it runs.

MCP servers (1)

• flowstate

  runs: flow mcp