@output.ai/cli 0.5.0 → 0.5.2

package/dist/templates/agent_instructions/skills/output-workflow-result/SKILL.md.template

@@ -8,7 +8,7 @@ allowed-tools: [Bash]
 
 ## Overview
 
-This skill retrieves the result (return value) of a completed workflow execution. Use it after a workflow started with `output workflow start` has completed, or to retrieve results from historical runs.
+This skill retrieves the result (return value) of a completed workflow execution. Use it after a workflow started with `npx output workflow start` has completed, or to retrieve results from historical runs.
 
 ## When to Use This Skill
 
@@ -22,14 +22,14 @@ This skill retrieves the result (return value) of a completed workflow execution
 
 - The workflow must have completed (status: COMPLETED)
 - You need the workflow ID
-- For FAILED workflows, use `output workflow debug` instead
+- For FAILED workflows, use `npx output workflow debug` instead
 
 ## Instructions
 
 ### Get Result
 
 ```bash
-output workflow result <workflowId>
+npx output workflow result <workflowId>
 ```
 
 The result is the return value of the workflow function, typically JSON.
@@ -39,10 +39,10 @@ The result is the return value of the workflow function, typically JSON.
 Before getting results, verify the workflow completed:
 
 ```bash
-output workflow status <workflowId>
+npx output workflow status <workflowId>
 # Should show: COMPLETED
 
-output workflow result <workflowId>
+npx output workflow result <workflowId>
 ```
 
 ## Understanding Results
@@ -62,7 +62,7 @@ export default workflow({
 
 ```bash
 # Result output
-output workflow result abc123
+npx output workflow result abc123
 # { "processed": true, "count": 42 }
 ```
 
@@ -70,13 +70,13 @@ output workflow result abc123
 
 If you try to get the result of a failed workflow:
 - You'll get an error message
-- Use `output workflow debug` instead to see what went wrong
+- Use `npx output workflow debug` instead to see what went wrong
 
 ### No Result (void workflows)
 
 Some workflows don't return a value:
 ```bash
-output workflow result abc123
+npx output workflow result abc123
 # null
 ```
 
@@ -86,15 +86,15 @@ output workflow result abc123
 
 ```bash
 # Start workflow
-output workflow start calculate '{"values": [1, 2, 3]}'
+npx output workflow start calculate '{"values": [1, 2, 3]}'
 # Output: Workflow ID: calc-abc123
 
 # Wait for completion
-output workflow status calc-abc123
+npx output workflow status calc-abc123
 # Status: COMPLETED
 
 # Get the result
-output workflow result calc-abc123
+npx output workflow result calc-abc123
 # { "sum": 6, "average": 2 }
 ```
 
@@ -102,21 +102,21 @@ output workflow result calc-abc123
 
 ```bash
 # Extract specific field
-output workflow result abc123 | jq '.total'
+npx output workflow result abc123 | jq '.total'
 
 # Format for display
-output workflow result abc123 | jq '.'
+npx output workflow result abc123 | jq '.'
 
 # Save to file
-output workflow result abc123 > result.json
+npx output workflow result abc123 > result.json
 ```
 
 **Scenario**: Compare results between runs
 
 ```bash
 # Get results from two runs
-output workflow result run-1-abc > result1.json
-output workflow result run-2-xyz > result2.json
+npx output workflow result run-1-abc > result1.json
+npx output workflow result run-2-xyz > result2.json
 
 # Compare
 diff result1.json result2.json
@@ -128,17 +128,17 @@ diff result1.json result2.json
 WORKFLOW_ID="abc123"
 
 # Wait for completion
-while [[ $(output workflow status $WORKFLOW_ID) == *"RUNNING"* ]]; do
+while [[ $(npx output workflow status $WORKFLOW_ID) == *"RUNNING"* ]]; do
   sleep 5
 done
 
 # Check if completed successfully
-if [[ $(output workflow status $WORKFLOW_ID) == *"COMPLETED"* ]]; then
-  RESULT=$(output workflow result $WORKFLOW_ID)
+if [[ $(npx output workflow status $WORKFLOW_ID) == *"COMPLETED"* ]]; then
+  RESULT=$(npx output workflow result $WORKFLOW_ID)
   echo "Workflow result: $RESULT"
 else
   echo "Workflow did not complete successfully"
-  output workflow debug $WORKFLOW_ID
+  npx output workflow debug $WORKFLOW_ID
 fi
 ```
 
@@ -146,25 +146,25 @@ fi
 
 ### JSON Objects
 ```bash
-output workflow result abc123
+npx output workflow result abc123
 # { "key": "value", "nested": { "data": true } }
 ```
 
 ### Arrays
 ```bash
-output workflow result abc123
+npx output workflow result abc123
 # [1, 2, 3, 4, 5]
 ```
 
 ### Primitive Values
 ```bash
-output workflow result abc123
+npx output workflow result abc123
 # 42
 
-output workflow result abc123
+npx output workflow result abc123
 # "success"
 
-output workflow result abc123
+npx output workflow result abc123
 # true
 ```
 
@@ -172,20 +172,20 @@ output workflow result abc123
 
 For large results, redirect to a file:
 ```bash
-output workflow result abc123 > large-result.json
+npx output workflow result abc123 > large-result.json
 ```
 
 ## Error Handling
 
 ### "Workflow not found"
 - Check the workflow ID is correct
-- Use `output workflow runs list` to find valid IDs
+- Use `npx output workflow runs list` to find valid IDs
 
 ### "Workflow not completed"
-- Check status: `output workflow status <id>`
+- Check status: `npx output workflow status <id>`
 - Wait for COMPLETED status before getting result
 - If RUNNING, wait and try again
-- If FAILED, use `output workflow debug`
+- If FAILED, use `npx output workflow debug`
 
 ### "No result available"
 - The workflow may return void/undefined
@@ -193,7 +193,7 @@ output workflow result abc123 > large-result.json
 
 ## Related Commands
 
-- `output workflow status <id>` - Check if workflow completed
-- `output workflow debug <id>` - Debug failed workflows
-- `output workflow run <name>` - Run and get result in one step
-- `output workflow runs list` - Find workflow IDs
+- `npx output workflow status <id>` - Check if workflow completed
+- `npx output workflow debug <id>` - Debug failed workflows
+- `npx output workflow run <name>` - Run and get result in one step
+- `npx output workflow runs list` - Find workflow IDs

package/dist/templates/agent_instructions/skills/output-workflow-run/SKILL.md.template

@@ -20,7 +20,7 @@ This skill executes a workflow synchronously, meaning the command waits for the
 
 ## When to Use Async Instead
 
-Consider using `output workflow start` (async) when:
+Consider using `npx output workflow start` (async) when:
 - The workflow takes a long time (minutes to hours)
 - You need to run multiple workflows in parallel
 - You want to disconnect and check results later
@@ -31,8 +31,8 @@ Consider using `output workflow start` (async) when:
 ### Basic Syntax
 
 ```bash
-output workflow run <workflowName> --input '<json-input>'
-output workflow run <workflowName> --input <path-to-json-file>
+npx output workflow run <workflowName> --input '<json-input>'
+npx output workflow run <workflowName> --input <path-to-json-file>
 ```
 
 The `--input` flag is required when the workflow expects input data.
@@ -44,7 +44,7 @@ The `--input` flag is required when the workflow expects input data.
 Pass JSON directly on the command line:
 
 ```bash
-output workflow run example --input '{"question": "who really is ada lovelace?"}'
+npx output workflow run example --input '{"question": "who really is ada lovelace?"}'
 ```
 
 #### 2. File Path (Recommended)
@@ -52,7 +52,7 @@ output workflow run example --input '{"question": "who really is ada lovelace?"}
 Reference a JSON file containing the input:
 
 ```bash
-output workflow run simple --input src/simple/scenarios/question_ada_lovelace.json
+npx output workflow run simple --input src/simple/scenarios/question_ada_lovelace.json
 ```
 
 This is the recommended approach because:
@@ -96,26 +96,26 @@ src/
 
 3. Run the workflow referencing the scenario:
    ```bash
-   output workflow run my_workflow --input src/my_workflow/scenarios/test_user.json
+   npx output workflow run my_workflow --input src/my_workflow/scenarios/test_user.json
    ```
 
 ### Input Examples
 
 ```bash
 # Inline JSON - simple object
-output workflow run my-workflow --input '{"userId": "123"}'
+npx output workflow run my-workflow --input '{"userId": "123"}'
 
 # Inline JSON - complex nested input
-output workflow run data-pipeline --input '{"source": "api", "options": {"limit": 100}}'
+npx output workflow run data-pipeline --input '{"source": "api", "options": {"limit": 100}}'
 
 # File path - reference a scenario file
-output workflow run simple --input src/simple/scenarios/basic.json
+npx output workflow run simple --input src/simple/scenarios/basic.json
 
 # File path - relative to current directory
-output workflow run batch-processor --input ./test_inputs/batch1.json
+npx output workflow run batch-processor --input ./test_inputs/batch1.json
 
 # No input (only if workflow doesn't require it)
-output workflow run health-check
+npx output workflow run health-check
 ```
 
 ## Understanding the Output
@@ -129,7 +129,7 @@ The workflow's return value is displayed, typically as JSON.
 If the workflow fails, you'll see:
 - Error message
 - The workflow ID (for further debugging)
-- Suggestion to use `output workflow debug` for details
+- Suggestion to use `npx output workflow debug` for details
 
 ## Examples
 
@@ -140,7 +140,7 @@ If the workflow fails, you'll see:
 ls src/simple/scenarios/
 
 # Run using a scenario file
-output workflow run simple --input src/simple/scenarios/basic_sum.json
+npx output workflow run simple --input src/simple/scenarios/basic_sum.json
 
 # Output:
 # { "sum": 6, "count": 3 }
@@ -158,20 +158,20 @@ cat > src/my_workflow/scenarios/test_case_1.json << 'EOF'
 EOF
 
 # Run the workflow
-output workflow run my_workflow --input src/my_workflow/scenarios/test_case_1.json
+npx output workflow run my_workflow --input src/my_workflow/scenarios/test_case_1.json
 ```
 
 **Scenario**: Quick inline test during development
 
 ```bash
-output workflow run example --input '{"question": "explain quantum computing"}'
+npx output workflow run example --input '{"question": "explain quantum computing"}'
 ```
 
 **Scenario**: Re-run a workflow with different input for debugging
 
 ```bash
 # First attempt with scenario file
-output workflow run process-data --input src/process_data/scenarios/user_abc.json
+npx output workflow run process-data --input src/process_data/scenarios/user_abc.json
 # Error occurs
 
 # Create a new scenario to isolate the issue
@@ -179,17 +179,17 @@ cat > src/process_data/scenarios/debug_minimal.json << 'EOF'
 {"id": "test", "debug": true}
 EOF
 
-output workflow run process-data --input src/process_data/scenarios/debug_minimal.json
+npx output workflow run process-data --input src/process_data/scenarios/debug_minimal.json
 ```
 
 **Scenario**: Capture output for further processing
 
 ```bash
 # Save result to a file
-output workflow run generate-report --input src/generate_report/scenarios/jan_2024.json > report.json
+npx output workflow run generate-report --input src/generate_report/scenarios/jan_2024.json > report.json
 
 # Pipe to jq for processing
-output workflow run get-users --input src/get_users/scenarios/active.json | jq '.users[].name'
+npx output workflow run get-users --input src/get_users/scenarios/active.json | jq '.users[].name'
 ```
 
 ## Error Handling
@@ -198,7 +198,7 @@ output workflow run get-users --input src/get_users/scenarios/active.json | jq '
 
 | Error | Cause | Solution |
 |-------|-------|----------|
-| "Workflow not found" | Workflow name is incorrect | Check with `output workflow list` |
+| "Workflow not found" | Workflow name is incorrect | Check with `npx output workflow list` |
 | "Invalid input" | JSON doesn't match schema | Verify input matches workflow's inputSchema |
 | "Parse error" | Malformed JSON or file not found | Check JSON syntax or file path |
 | "Timeout" | Workflow took too long | Use async execution for long workflows |
@@ -208,10 +208,10 @@ output workflow run get-users --input src/get_users/scenarios/active.json | jq '
 When a workflow fails, the output includes the workflow ID. Use it to get the full trace:
 
 ```bash
-output workflow run my-workflow --input src/my_workflow/scenarios/test.json
+npx output workflow run my-workflow --input src/my_workflow/scenarios/test.json
 # Output: Workflow failed. ID: abc123xyz
 
-output workflow debug abc123xyz --format json
+npx output workflow debug abc123xyz --format json
 ```
 
 ## Input Schema Tips
@@ -223,6 +223,6 @@ output workflow debug abc123xyz --format json
 
 ## Related Commands
 
-- `output workflow start <name> --input` - Start asynchronously
-- `output workflow list` - See available workflows
-- `output workflow debug <id>` - Debug a failed run
+- `npx output workflow start <name> --input` - Start asynchronously
+- `npx output workflow list` - See available workflows
+- `npx output workflow debug <id>` - Debug a failed run

package/dist/templates/agent_instructions/skills/output-workflow-runs-list/SKILL.md.template

@@ -23,7 +23,7 @@ This skill helps you view the execution history of workflows. Use it to find fai
 ### List All Recent Runs
 
 ```bash
-output workflow runs list
+npx output workflow runs list
 ```
 
 By default, this shows the 100 most recent workflow executions across all workflow types.
@@ -38,7 +38,7 @@ By default, this shows the 100 most recent workflow executions across all workfl
 ### Filter by Workflow Name
 
 ```bash
-output workflow runs list <workflowName>
+npx output workflow runs list <workflowName>
 ```
 
 This shows only runs for the specified workflow type.
@@ -46,7 +46,7 @@ This shows only runs for the specified workflow type.
 ### Get Detailed JSON Output
 
 ```bash
-output workflow runs list --format json
+npx output workflow runs list --format json
 ```
 
 Use JSON format for programmatic analysis or when you need full details.
@@ -79,42 +79,42 @@ When viewing runs, pay attention to:
 
 ```bash
 # List recent runs and look for FAILED status
-output workflow runs list --limit 20
+npx output workflow runs list --limit 20
 
 # Or use JSON format with jq to filter
-output workflow runs list --format json | jq '.[] | select(.status == "FAILED")'
+npx output workflow runs list --format json | jq '.[] | select(.status == "FAILED")'
 ```
 
 **Scenario**: Get workflow ID for debugging
 
 ```bash
 # List runs for a specific workflow
-output workflow runs list my-workflow --limit 5
+npx output workflow runs list my-workflow --limit 5
 
 # Note the workflow ID from the output (e.g., "abc123xyz")
 # Then debug it
-output workflow debug abc123xyz --format json
+npx output workflow debug abc123xyz --format json
 ```
 
 **Scenario**: Review recent activity for a specific workflow
 
 ```bash
 # See the last 10 runs of the data-pipeline workflow
-output workflow runs list data-pipeline --limit 10
+npx output workflow runs list data-pipeline --limit 10
 ```
 
 **Scenario**: Export run history for analysis
 
 ```bash
 # Get all recent runs as JSON for external analysis
-output workflow runs list --format json > workflow-runs.json
+npx output workflow runs list --format json > workflow-runs.json
 ```
 
 **Scenario**: Find when failures started
 
 ```bash
 # Look at more history to find patterns
-output workflow runs list --limit 50 --format json | jq 'group_by(.status) | map({status: .[0].status, count: length})'
+npx output workflow runs list --limit 50 --format json | jq 'group_by(.status) | map({status: .[0].status, count: length})'
 ```
 
 ## Identifying Problems
@@ -129,13 +129,13 @@ output workflow runs list --limit 50 --format json | jq 'group_by(.status) | map
 ### Next Steps After Finding a Failed Run
 
 1. Copy the workflow ID from the run
-2. Get the execution trace: `output workflow debug <workflowId> --format json`
+2. Get the execution trace: `npx output workflow debug <workflowId> --format json`
 3. Analyze the trace to identify the failure
 4. Apply the appropriate fix based on the error pattern
 
 ## Related Commands
 
-- `output workflow debug <id>` - Analyze execution trace
-- `output workflow status <id>` - Check current status
-- `output workflow result <id>` - Get execution result
-- `output workflow list` - List available workflows
+- `npx output workflow debug <id>` - Analyze execution trace
+- `npx output workflow status <id>` - Check current status
+- `npx output workflow result <id>` - Get execution result
+- `npx output workflow list` - List available workflows

package/dist/templates/agent_instructions/skills/output-workflow-start/SKILL.md.template

@@ -20,7 +20,7 @@ This skill starts a workflow asynchronously, meaning the command returns immedia
 
 ## When to Use Sync Instead
 
-Consider using `output workflow run` (sync) when:
+Consider using `npx output workflow run` (sync) when:
 - Workflow completes quickly (seconds)
 - You need the result immediately in your terminal
 - Simple testing during development
@@ -31,8 +31,8 @@ Consider using `output workflow run` (sync) when:
 ### Basic Syntax
 
 ```bash
-output workflow start <workflowName> --input '<json-input>'
-output workflow start <workflowName> --input <path-to-json-file>
+npx output workflow start <workflowName> --input '<json-input>'
+npx output workflow start <workflowName> --input <path-to-json-file>
 ```
 
 The `--input` flag is required when the workflow expects input data.
@@ -44,7 +44,7 @@ The `--input` flag is required when the workflow expects input data.
 Pass JSON directly on the command line:
 
 ```bash
-output workflow start data-migration --input '{"batchSize": 1000}'
+npx output workflow start data-migration --input '{"batchSize": 1000}'
 ```
 
 #### 2. File Path (Recommended)
@@ -52,7 +52,7 @@ output workflow start data-migration --input '{"batchSize": 1000}'
 Reference a JSON file containing the input:
 
 ```bash
-output workflow start data-migration --input src/data_migration/scenarios/large_batch.json
+npx output workflow start data-migration --input src/data_migration/scenarios/large_batch.json
 ```
 
 This is the recommended approach because:
@@ -63,30 +63,30 @@ This is the recommended approach because:
 ### Getting the Workflow ID
 
 The command outputs the workflow ID which you'll need for:
-- Checking status: `output workflow status <id>`
-- Getting results: `output workflow result <id>`
-- Debugging: `output workflow debug <id>`
+- Checking status: `npx output workflow status <id>`
+- Getting results: `npx output workflow result <id>`
+- Debugging: `npx output workflow debug <id>`
 
 ## Examples
 
 **Scenario**: Start a long-running workflow with scenario file
 
 ```bash
-output workflow start data-migration --input src/data_migration/scenarios/full_migration.json
+npx output workflow start data-migration --input src/data_migration/scenarios/full_migration.json
 
 # Output:
 # Started workflow: data-migration
 # Workflow ID: abc123xyz
-# Use 'output workflow status abc123xyz' to check progress
+# Use 'npx output workflow status abc123xyz' to check progress
 ```
 
 **Scenario**: Start multiple workflows in parallel using scenario files
 
 ```bash
 # Start several workflows with different scenario files
-output workflow start process-batch --input src/process_batch/scenarios/batch_1.json
-output workflow start process-batch --input src/process_batch/scenarios/batch_2.json
-output workflow start process-batch --input src/process_batch/scenarios/batch_3.json
+npx output workflow start process-batch --input src/process_batch/scenarios/batch_1.json
+npx output workflow start process-batch --input src/process_batch/scenarios/batch_2.json
+npx output workflow start process-batch --input src/process_batch/scenarios/batch_3.json
 
 # Note: Save the workflow IDs to check them later
 ```
@@ -105,37 +105,37 @@ cat > src/generate_report/scenarios/annual_2024.json << 'EOF'
 EOF
 
 # Start the workflow
-output workflow start generate-report --input src/generate_report/scenarios/annual_2024.json
+npx output workflow start generate-report --input src/generate_report/scenarios/annual_2024.json
 # Output: Workflow ID: report-2024-abc
 
 # Check status periodically
-output workflow status report-2024-abc
+npx output workflow status report-2024-abc
 # Output: Status: RUNNING
 
 # Later, check again
-output workflow status report-2024-abc
+npx output workflow status report-2024-abc
 # Output: Status: COMPLETED
 
 # Get the result
-output workflow result report-2024-abc
+npx output workflow result report-2024-abc
 ```
 
 **Scenario**: Quick inline test for development
 
 ```bash
-output workflow start quick-job --input '{"test": true}'
+npx output workflow start quick-job --input '{"test": true}'
 ```
 
 **Scenario**: Script for parallel execution
 
 ```bash
 # Start workflows and capture IDs
-ID1=$(output workflow start job --input src/job/scenarios/type_a.json | grep "Workflow ID" | cut -d: -f2 | tr -d ' ')
-ID2=$(output workflow start job --input src/job/scenarios/type_b.json | grep "Workflow ID" | cut -d: -f2 | tr -d ' ')
+ID1=$(npx output workflow start job --input src/job/scenarios/type_a.json | grep "Workflow ID" | cut -d: -f2 | tr -d ' ')
+ID2=$(npx output workflow start job --input src/job/scenarios/type_b.json | grep "Workflow ID" | cut -d: -f2 | tr -d ' ')
 
 # Wait and check results
-output workflow result $ID1
-output workflow result $ID2
+npx output workflow result $ID1
+npx output workflow result $ID2
 ```
 
 ## Following Up After Starting
@@ -143,7 +143,7 @@ output workflow result $ID2
 ### Check Status
 
 ```bash
-output workflow status <workflowId>
+npx output workflow status <workflowId>
 ```
 
 Status values:
@@ -155,7 +155,7 @@ Status values:
 ### Get Result
 
 ```bash
-output workflow result <workflowId>
+npx output workflow result <workflowId>
 ```
 
 Only works for COMPLETED workflows. For FAILED workflows, use debug.
@@ -163,13 +163,13 @@ Only works for COMPLETED workflows. For FAILED workflows, use debug.
 ### Debug If Failed
 
 ```bash
-output workflow debug <workflowId> --format json
+npx output workflow debug <workflowId> --format json
 ```
 
 ### Stop If Needed
 
 ```bash
-output workflow stop <workflowId>
+npx output workflow stop <workflowId>
 ```
 
 ## Workflow ID Management
@@ -178,8 +178,8 @@ When starting multiple workflows, keep track of IDs:
 
 ```bash
 # Log IDs to a file
-output workflow start batch-job --input src/batch_job/scenarios/id_1.json >> workflow-ids.txt
-output workflow start batch-job --input src/batch_job/scenarios/id_2.json >> workflow-ids.txt
+npx output workflow start batch-job --input src/batch_job/scenarios/id_1.json >> workflow-ids.txt
+npx output workflow start batch-job --input src/batch_job/scenarios/id_2.json >> workflow-ids.txt
 
 # Or use a naming convention in your workflow that makes IDs predictable
 ```
@@ -188,14 +188,14 @@ output workflow start batch-job --input src/batch_job/scenarios/id_2.json >> wor
 
 1. **Use scenario files**: Store inputs in `src/<workflow>/scenarios/` for reproducibility
 2. **Save the workflow ID**: Always note the ID for later reference
-3. **Monitor long workflows**: Use `output workflow status` to check progress
+3. **Monitor long workflows**: Use `npx output workflow status` to check progress
 4. **Handle failures**: Check status before getting results
-5. **Clean up**: Stop any stuck workflows with `output workflow stop`
+5. **Clean up**: Stop any stuck workflows with `npx output workflow stop`
 
 ## Related Commands
 
-- `output workflow run <name> --input` - Execute synchronously
-- `output workflow status <id>` - Check execution status
-- `output workflow result <id>` - Get execution result
-- `output workflow stop <id>` - Stop a running workflow
-- `output workflow debug <id>` - Debug a workflow execution
+- `npx output workflow run <name> --input` - Execute synchronously
+- `npx output workflow status <id>` - Check execution status
+- `npx output workflow result <id>` - Get execution result
+- `npx output workflow stop <id>` - Stop a running workflow
+- `npx output workflow debug <id>` - Debug a workflow execution