ax-flow

Generate AxFlow workflow code with @ax-llm/ax for parallel and conditional AI tasks.

1|1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/jadecli/researchers --skill ax-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ax-flow
Source: https://github.com/jadecli/researchers/tree/main/agentcrawls-ts/.claude/skills/ax-flow
Command: npx skills add https://github.com/jadecli/researchers --skill ax-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of correct AxFlow workflow code using the @ax-llm/ax library, reducing manual errors in complex flow orchestration across nodes and parallel tasks.

Core Features & Use Cases

  • Generates AxFlow workflow code from user prompts for multi-node AI pipelines.
  • Supports parallel execution, conditional branching, and map/reduce style workflows.
  • Real-world usage includes designing DAG-like pipelines with branching and merging outputs.

Quick Start

Provide a concise AxFlow workflow definition that demonstrates a basic parallel flow with conditional routing.

Frequently Asked Questions about ax-flow

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

FAQPage Schema
How do I generate TypeScript code for parallel AI pipelines?

To generate TypeScript code for parallel AI pipelines, use the flow() factory to define nodes and apply proper .node() ordering. This creates deterministic DAG workflows by executing parallel AI tasks before calling .execute() and .returns().

What is the best way to orchestrate conditional branching in AI workflows?

The best way to orchestrate conditional branching in AI workflows is using map/reduce patterns with correct branching and merging outputs. This ensures deterministic execution across multi-node pipelines without manual flow routing errors.

How do I build a DAG workflow with TypeScript for LLM orchestration?

You build a DAG workflow with TypeScript for LLM orchestration by using the flow() factory to structure multi-node pipelines. Defining proper .node() ordering and branching creates deterministic execution paths for complex AI tasks.

Why does my workflow code fail when routing parallel AI tasks?

Workflow code fails when routing parallel AI tasks if .execute() is not called before .returns() or if branching and merging are incorrect. Proper .node() ordering is required to ensure deterministic execution across the pipeline.

Can I use map/reduce patterns for multi-node AI pipelines?

Yes, you can use map/reduce patterns for multi-node AI pipelines. By applying the flow() factory with proper node ordering and merging, you can orchestrate complex DAG-like workflows with deterministic execution.