skills.rest
growthxai
growthxaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

output-dev-step-function

Define deterministic modular step workflows for Output SDK projects.

430|12|Updated Mar 13, 2026
Search Tags:#typescript#llm#error-handling#output-sdk#http-client#step-function
One-click install
npx skills add https://github.com/growthxai/output --skill output-dev-step-function
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: output-dev-step-function
Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-step-function
Command: npx skills add https://github.com/growthxai/output --skill output-dev-step-function

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured, reusable steps for Output SDK workflows to manage I/O, HTTP, and LLM calls with deterministic replay and robust error handling.

Core Features & Use Cases

  • Define steps in steps.ts or a steps/ folder; enforce path-based step definitions; set input/output schemas; integrate with HTTP and LLM clients; manage errors with FatalError and ValidationError; enable step reusability and maintainability.
  • Use for I/O operations, error handling, HTTP requests, or LLM calls within Output SDK workflows.
  • Real-world example: separate a data fetch step, an API call step, and a validation step for a robust data pipeline.

Quick Start

Create your first workflow by exporting a step in your workflow's steps file using the standard step pattern.

Frequently Asked Questions about output-dev-step-function

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

FAQPage Schema
How do I structure deterministic step workflows in TypeScript for Output SDK?▼

You define deterministic step workflows by creating steps in a steps.ts file or steps/ folder, enforcing path-based placement, and setting input/output schemas for I/O, HTTP, and LLM interactions.

What is the best way to handle errors in Output SDK TypeScript workflows?▼

Error handling in Output SDK workflows is managed using FatalError and ValidationError classes to categorize failures across IO, HTTP, and LLM step interactions robustly.

Can I separate HTTP requests and LLM interactions into modular steps?▼

Yes, separating HTTP requests and LLM interactions into modular steps enables independent data fetching, API calls, and validation for a robust and reusable data pipeline.

Do I need to define input and output schemas for every step in an Output SDK workflow?▼

Defining input and output schemas for every step in Output SDK workflows is enforced to ensure deterministic replay and maintain step reusability and maintainability.

Why should I use path-based step definitions instead of inline functions?▼

Path-based step definitions enforce strict ES module import conventions, ensuring step reusability and deterministic replay across TypeScript workflows instead of using inline functions.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
nadicodeainadicodeai

guidance

Constrain LLM outputs with regex and grammars for structured JSON or XML.

Official
Advanced
stacksjsstacksjs
622

stacks-http

Configure HTTP clients and handle responses in Stacks apps with TypeScript.

Official
Intermediate
evengulevengul

docs-development

Document MC-ORG pipeline orchestration, database operations, and validation patterns.

Community
Intermediate