foxctl Flow Engine

Execute JSON envelope DAGs to orchestrate multi-agent development workflows.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-flow-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl Flow Engine
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills/foxctl-flow
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-flow-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of coordinating multi-step AI workflows by turning loosely connected agent steps into an explicit, runnable flow graph with reliable state and routing.

Core Features & Use Cases

  • DAG-based flow orchestration: Build DAGs where agent, transform, and skill nodes consume and produce JSON envelopes, with edges that can apply transforms and conditions.
  • Push-mode structured outputs: Let agent nodes publish structured JSON back into the engine, triggering downstream nodes automatically.
  • Daemon-backed execution and isolation: Run flows through a per-workspace daemon for long-lived execution, caching, and agent spawns with robust logging and status tracking.

Quick Start

Create a flow, add an agent node in push output mode that researches a topic, add a file_write transform node that saves the resulting report to disk, connect them with an edge, and start the flow in your workspace.

Frequently Asked Questions about foxctl Flow Engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-agent development workflows with deterministic routing?

You orchestrate multi-agent development workflows by executing JSON envelope DAGs with agents, transforms, and skills. Intermediate outputs deterministically route through downstream steps via push-mode output routing, ensuring reliable state and structured report generation.

What is push-mode output routing in a multi-agent pipeline?

Push-mode output routing lets agent nodes publish structured JSON back into the engine, automatically triggering downstream nodes. This mechanism turns loosely connected agent steps into an explicit, runnable flow graph with reliable state and routing.

How do I structure a flow graph for multi-step agent pipelines?

You structure a flow graph using JSON envelope DAGs with node and edge definitions. Agent, transform, and skill nodes consume and produce JSON envelopes, while edges apply transforms and conditions to route intermediate outputs deterministically.

Can I run long-lived multi-agent workflows with caching and isolation?

Yes, you can run long-lived multi-agent workflows through a per-workspace daemon. This daemon-backed execution provides caching, agent spawns, and robust logging, status tracking, and error handling for your flow orchestration.

When should I use JSON DAGs for multi-agent workflow orchestration?

Use JSON DAGs for research pipelines, structured report generation, and automation where intermediate outputs must deterministically route through downstream steps. It solves the challenge of coordinating multi-step AI workflows with reliable state and routing.

How do I start a basic research and file writing automation workflow?

Create a flow, add an agent node in push output mode that researches a topic, add a file_write transform node that saves the resulting report to disk, connect them with an edge, and start the flow in your workspace.