← ClaudeAtlas

workflowslisted

Manage custom YAML workflow definitions for orchestration
palginpav/orchestray · ★ 0 · AI & Automation · score 71
Install: claude install-skill palginpav/orchestray
# Workflow Management The user wants to manage custom workflow definitions that describe multi-step orchestration sequences. ## Protocol 1. **Parse arguments**: `$ARGUMENTS` - If empty or "list": Show all workflows in table format - If starts with "create": Create a new workflow interactively - If starts with "validate": Validate a named workflow file - If starts with "delete": Delete a named workflow with confirmation - Otherwise: treat as a workflow name and show its details ### List Operation Glob `.orchestray/workflows/*.yaml`. If the directory does not exist or no files are found, report: "No workflows found. Use `/orchestray:workflows create <name>` to define one." For each file found, read the top-level `name`, `description`, and count the `steps` array. Display a table: ``` | Name | Description | Steps | Created | |------|-------------|-------|---------| | {name} | {description} | {N} | {created_at} | ``` Below the table, show: "{N} workflow(s) found." Then show usage hints: - `create <name>` -- Define a new workflow - `<name>` -- Show full workflow details - `validate <name>` -- Check a workflow for errors - `delete <name>` -- Remove a workflow ### Show Operation Parse the workflow name from arguments. Look for `.orchestray/workflows/{name}.yaml`. If neither exists, glob `.orchestray/workflows/` and suggest alternatives: "Workflow '{name}' not found. Available: {list}." If no workflows exist: "Workflow '{name}' not found. No workflows define