fsd:add-flow

Create flow definitions with action blocks and server registration configurations.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/fixpoint-labs/flow-state-dev --skill fsd-add-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fsd:add-flow
Source: https://github.com/fixpoint-labs/flow-state-dev/tree/main/.agents/skills/add-flow
Command: npx skills add https://github.com/fixpoint-labs/flow-state-dev --skill fsd-add-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @flow-state-dev/core, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of creating new flow definitions in the flow-state-dev framework, ensuring consistent structure and ease of development.

Core Features & Use Cases

  • Flow Definition Creation: Automatically generate flow files, action blocks, and server registration configurations.
  • Action Definition: Customize actions with input schemas, block pipelines, and user message handling.
  • Scope State Management: Declare and manage session, user, and project states with schema definitions.
  • Resource Management: Define and use typed data containers for structured entities and resources.
  • Use Case: Develop a multi-action flow that incorporates chat functionality, session state management, and client data projections for a comprehensive user experience.

Quick Start

To create a new flow, run the add-flow skill with the desired flow kind and purpose as an argument, such as 'add-flow "customer support flow with chat and summary actions"'

Frequently Asked Questions about fsd:add-flow

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

FAQPage Schema
How do I automate flow definition creation for complex AI-driven processes?

Automating flow definition creation involves generating structured flow files, action blocks, and server registration configurations to orchestrate scalable AI processes. This ensures consistent structure and streamlines the development of complex workflows.

How does scope state management work when building multi-action flows?

Scope state management in multi-action flows works by declaring and managing session, user, and project states with schema definitions. This allows you to maintain persistent context and manage data projections throughout the workflow lifecycle.

Can I customize action definitions with input schemas and block pipelines?

You can customize action definitions by specifying input schemas, configuring block pipelines, and handling user messages. This enables tailored interactions within the flow-state-dev framework for comprehensive user experiences.

What is the best way to define typed data containers for structured resources in a development workflow?

Defining typed data containers for structured resources involves declaring specific entities within the flow definition. This approach manages resource allocation effectively and ensures data consistency across complex, scalable workflows.

Do I need the core framework to orchestrate actions and resource allocation?

You need the core framework to orchestrate actions and resource allocation. The flow-state-dev core dependency provides the foundational environment required to manage state and execute the generated flow definitions.

What are the limitations of manual flow definition for scalable state management?

Manual flow definition for scalable state management often leads to structural inconsistencies and development bottlenecks. Automating the creation of flow files and action blocks ensures consistent architecture and reduces configuration errors.