List all available Output SDK workflows in the project. Use when discovering what workflows exist, checking workflow names, exploring the project's workflow structure, or when unsure which workflows are available to run.
List all available Output SDK workflows in the project. Use when discovering what workflows exist, checking workflow names, or exploring the project's workflow structure.
/plugin marketplace add growthxai/output-claude-plugins/plugin install growthxai-outputai-plugins-outputai@growthxai/output-claude-pluginsThis skill is limited to using the following tools:
This skill helps you discover all available workflows in an Output SDK project. Workflows are the main execution units that orchestrate steps to accomplish tasks.
npx output workflow list
This command scans the project and displays all available workflows.
The command outputs a table with workflow information:
| Column | Description |
|---|---|
| Name | The workflow identifier used in commands |
| Description | Brief description of what the workflow does |
| Location | File path where the workflow is defined |
Workflows are typically located in:
src/workflows/*/
Each workflow directory usually contains:
workflow.ts or index.ts - The main workflow definitionAfter finding a workflow, you can examine its code:
# Read the workflow file
cat src/workflows/<workflowName>/workflow.ts
# Or examine the entire workflow directory
ls -la src/workflows/<workflowName>/
Scenario: Discover available workflows in a project
npx output workflow list
# Example output:
# Name Description Location
# ----------- --------------------------- --------------------------------
# simple Simple workflow example src/workflows/simple/workflow.ts
# data-pipeline Process and transform data src/workflows/data-pipeline/workflow.ts
# user-signup Handle user registration src/workflows/user-signup/workflow.ts
Scenario: Verify a workflow exists before running
# Check if "email-sender" workflow exists
npx output workflow list | grep email-sender
# If no output, the workflow doesn't exist
# If found, proceed with running it
npx output workflow run email-sender '{"to": "user@example.com"}'
Scenario: Explore workflow implementation
# List workflows
npx output workflow list
# Find the location and examine it
cat src/workflows/simple/workflow.ts
src/workflows/*/npm run output:workflow:build to check for TypeScript errorsnpx output workflow run <name> - Execute a workflow synchronouslynpx output workflow start <name> - Start a workflow asynchronouslynpx output workflow runs list - View execution historyThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.