new-exec-type
SkillFiles & storageAdd a new executable type to the flow runner (a new kind of automation block users can define in .flow files).
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the new-exec-type skill
What this skill tells your AI
The instructions your AI receives, as published by flowexec/flow in .claude/skills/new-exec-type/SKILL.md and read by ahel’s review.
Add a new executable type to the flow runner for: $ARGUMENTS
An "executable type" is a new automation block users can declare in .flow files (like exec, serial, parallel, render). Follow these steps in order:
-
Schema first — add the new type's fields to
types/executable/executable_schema.yaml. Read the existing schema to match the structure. Regenerate with thegenerateexecutable (mcp__flow__execute, refgenerate) — it rewritestypes/executable/executable.gen.go. Never edit the.gen.gofile directly. -
Runner handler — each type is its own package: create
internal/runner/<type>/<type>.go. Readinternal/runner/exec/exec.goorinternal/runner/serial/serial.goas reference for the exact interface and pattern. -
Register the type — wire the new handler into
internal/runner/runner.go(the dispatch table). -
Parser support — update
internal/fileparser/if needed to recognize and validate the new type during YAML parsing. -
Tests — add unit tests in
internal/runner/<type>/<type>_test.gousing Ginkgo. UseDescribe/It/Entry— neverFDescribe/FIt. Cover happy path and error cases. -
Validate — run the
validateexecutable (mcp__flow__execute, refvalidate) to confirm generate, lint, and tests all pass.
Do not skip the schema step — editing generated files directly will cause CI to fail.
Signals
- GitHub stars
- 136
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
new-exec-type- Source
- github.com/flowexec/flow