agno-workflows-basic

Orchestrates sequential Agno Workflows with Steps executed by Agents, Teams, or functions.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/allankltsn/setup_kiro --skill agno-workflows-basic-allankltsn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agno-workflows-basic
Source: https://github.com/allankltsn/setup_kiro/tree/main/.kiro/skills/agno-workflows-basic
Command: npx skills add https://github.com/allankltsn/setup_kiro --skill agno-workflows-basic-allankltsn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agno.

What problem does it solve? Building multi-step AI pipelines often requires predictable, repeatable execution order, but dynamic agent teams decide routing at runtime. This Skill teaches how to define deterministic Agno Workflows where Steps run in a fixed sequence with persisted session state. ## Core Features & Use Cases - Sequential Workflow Orchestration: Chain Steps executed by Agents, Teams, or custom Python functions using the Workflow and Step classes. - Step Input/Output Handling: Access the original input, previous step outputs, and named step results via StepInput and StepOutput. - Deterministic Quality Gates: Insert custom executor functions that validate content and can stop the pipeline early. - Use Case: Build a research-to-writing pipeline where a Researcher agent's output feeds a Writer agent, with a function-based quality gate rejecting content under 200 characters, all persisted in a SQLite session database. ## Quick Start Ask the AI to create an Agno Workflow with two sequential Steps, a researcher agent followed by a writer agent, persisted with SqliteDb.

Frequently Asked Questions about agno-workflows-basic

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

FAQPage Schema
How do I create a sequential workflow with Agno agents?▼

Create a Workflow with a list of Step objects, each referencing an Agent, and call print_response to run them in order. Each step's output automatically becomes context for the next step in the sequence.

What is the difference between Agno Workflow and Team?▼

A Workflow executes Steps in a fixed, predefined order you control, making it predictable and repeatable. A Team has a leader that decides routing dynamically at runtime, which suits scenarios where the decision path is not known in advance.

How do I access previous step outputs in an Agno workflow function?▼

Use the StepInput parameter inside your executor function. It provides previous_step_content for the last output, get_step_content with a step name for a specific result, and get_all_previous_content for everything.

Can an Agno workflow step stop the pipeline early?▼

Yes, a custom executor function can return a StepOutput with stop set to True and success set to False. This is useful for quality gates, such as rejecting content shorter than a minimum length before later steps run.

Does Agno Workflow support running a Team as a single step?▼

Yes, pass the team to the Step constructor using the team parameter instead of agent. The entire Team then executes as one step within the sequential workflow, combining dynamic routing with deterministic ordering.