create-workflow

Extract SKILL.md frontmatter metadata into a YAML catalog document.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HyperDev1/hx-ai --skill create-workflow-hyperdev1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-workflow
Source: https://github.com/HyperDev1/hx-ai/tree/main/src/resources/skills/create-workflow
Command: npx skills add https://github.com/HyperDev1/hx-ai --skill create-workflow-hyperdev1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Create workflow unit helps teams consistently design and deploy HX workflow definitions by converting conversational prompts into structured YAML definitions that HX can execute.

Core Features & Use Cases

  • Provides a guided, phase-based approach to defining steps, dependencies, context, and verification.
  • Supports parameterization, iteration, and advanced verification patterns to build robust automation.
  • Ideal for building reusable workflows for code generation, data processing, and release pipelines.

Quick Start

Create a complete YAML workflow definition from a user goal following the template.

Frequently Asked Questions about create-workflow

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

FAQPage Schema
How do I turn a prompt into a YAML workflow definition?

To turn a prompt into a YAML workflow definition, you extract the skill's identity, scope, and artifacts from its metadata and assemble them into a single YAML document. This process converts conversational goals into structured YAML ready for catalog ingestion.

What is the best way to define automation steps and dependencies in YAML?

Defining automation steps and dependencies in YAML requires a guided, phase-based approach to structure context and verification. This method assembles metadata fields including name, tagline, dependencies, and components into a structured definition.

Can I parameterize workflows for code generation and data processing pipelines?

You can parameterize workflows for code generation and data processing pipelines by extracting scope and artifacts from skill metadata. This supports parameterization, iteration, and advanced verification patterns to build robust, repeatable automation.

Does the HX engine require specific metadata fields for workflow ingestion?

The HX engine requires specific metadata fields for workflow ingestion, including name, tagline, description, request, complexity, category, keywords, dependencies, and components. These fields are extracted and presented as a single YAML document.

What are the limitations of extracting skill metadata for workflow generation?

Limitations of extracting skill metadata include relying entirely on the SKILL.md frontmatter and adjacent content for accurate identity and scope. The workflow generation cannot infer missing parameters or verify external dependencies not defined in the metadata.