@output.ai/cli 0.5.0 → 0.5.2

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

@@ -20,27 +20,27 @@ This skill checks the current execution status of a workflow. Use it to monitor
 
 ## When to Use Other Commands
 
-- **Getting results**: Use `output workflow result` after confirming COMPLETED status
-- **Debugging failures**: Use `output workflow debug` for FAILED workflows
-- **Execution history**: Use `output workflow runs list` for multiple runs
+- **Getting results**: Use `npx output workflow result` after confirming COMPLETED status
+- **Debugging failures**: Use `npx output workflow debug` for FAILED workflows
+- **Execution history**: Use `npx output workflow runs list` for multiple runs
 
 ## Instructions
 
 ### Check Status
 
 ```bash
-output workflow status <workflowId>
+npx output workflow status <workflowId>
 ```
 
-Replace `<workflowId>` with the ID from `output workflow start` or `output workflow runs list`.
+Replace `<workflowId>` with the ID from `npx output workflow start` or `npx output workflow runs list`.
 
 ## Understanding Status Values
 
 | Status | Meaning | Next Action |
 |--------|---------|-------------|
 | RUNNING | Workflow is currently executing | Wait and check again |
-| COMPLETED | Workflow finished successfully | Get result with `output workflow result` |
-| FAILED | Workflow encountered an error | Debug with `output workflow debug` |
+| COMPLETED | Workflow finished successfully | Get result with `npx output workflow result` |
+| FAILED | Workflow encountered an error | Debug with `npx output workflow debug` |
 | TERMINATED | Workflow was manually stopped | Review if expected, restart if needed |
 | TIMED_OUT | Workflow exceeded time limit | Check for long operations, adjust timeout |
 
@@ -50,16 +50,16 @@ Replace `<workflowId>` with the ID from `output workflow start` or `output workf
 
 ```bash
 # Start a workflow
-output workflow start data-sync '{"source": "external"}'
+npx output workflow start data-sync '{"source": "external"}'
 # Output: Workflow ID: sync-abc123
 
 # Check status
-output workflow status sync-abc123
+npx output workflow status sync-abc123
 # Output: Status: RUNNING
 
 # Wait and check again
 sleep 30
-output workflow status sync-abc123
+npx output workflow status sync-abc123
 # Output: Status: COMPLETED
 ```
 
@@ -69,16 +69,16 @@ output workflow status sync-abc123
 WORKFLOW_ID="abc123xyz"
 
 while true; do
-  STATUS=$(output workflow status $WORKFLOW_ID)
+  STATUS=$(npx output workflow status $WORKFLOW_ID)
   echo "Current status: $STATUS"
 
   if [[ "$STATUS" == *"COMPLETED"* ]]; then
     echo "Workflow completed!"
-    output workflow result $WORKFLOW_ID
+    npx output workflow result $WORKFLOW_ID
     break
   elif [[ "$STATUS" == *"FAILED"* ]]; then
     echo "Workflow failed!"
-    output workflow debug $WORKFLOW_ID --format json
+    npx output workflow debug $WORKFLOW_ID --format json
     break
   fi
 
@@ -90,13 +90,13 @@ done
 
 ```bash
 # Verify status first
-output workflow status my-workflow-123
+npx output workflow status my-workflow-123
 
 # If COMPLETED, get result
-output workflow result my-workflow-123
+npx output workflow result my-workflow-123
 
 # If FAILED, debug instead
-output workflow debug my-workflow-123 --format json
+npx output workflow debug my-workflow-123 --format json
 ```
 
 **Scenario**: Batch status check
@@ -104,7 +104,7 @@ output workflow debug my-workflow-123 --format json
 ```bash
 # Check multiple workflows
 for id in abc123 def456 ghi789; do
-  echo "Workflow $id: $(output workflow status $id)"
+  echo "Workflow $id: $(npx output workflow status $id)"
 done
 ```
 
@@ -131,21 +131,21 @@ The status command returns information including:
 ### "Workflow not found"
 - The workflow ID may be incorrect
 - The workflow may have been deleted from history
-- Check `output workflow runs list` to find the correct ID
+- Check `npx output workflow runs list` to find the correct ID
 
 ### Status stays RUNNING too long
-1. Check if the workflow is stuck: `output workflow debug <id>`
+1. Check if the workflow is stuck: `npx output workflow debug <id>`
 2. Look for infinite loops or waiting operations
-3. Consider stopping: `output workflow stop <id>`
+3. Consider stopping: `npx output workflow stop <id>`
 
 ### Unexpected TERMINATED status
 - Someone may have manually stopped the workflow
-- Check with `output workflow debug` for context
-- Restart if needed: `output workflow start`
+- Check with `npx output workflow debug` for context
+- Restart if needed: `npx output workflow start`
 
 ## Related Commands
 
-- `output workflow result <id>` - Get execution result (after COMPLETED)
-- `output workflow debug <id>` - Debug execution (after FAILED)
-- `output workflow stop <id>` - Stop a running workflow
-- `output workflow runs list` - View execution history
+- `npx output workflow result <id>` - Get execution result (after COMPLETED)
+- `npx output workflow debug <id>` - Debug execution (after FAILED)
+- `npx output workflow stop <id>` - Stop a running workflow
+- `npx output workflow runs list` - View execution history

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

@@ -22,7 +22,7 @@ This skill stops a running workflow execution. The workflow will be marked as TE
 
 - If the workflow is about to complete (let it finish)
 - If you're unsure whether stopping is safe
-- For debugging (use `output workflow debug` instead)
+- For debugging (use `npx output workflow debug` instead)
 - If the workflow has side effects that may leave data in an inconsistent state
 
 ## Instructions
@@ -30,7 +30,7 @@ This skill stops a running workflow execution. The workflow will be marked as TE
 ### Stop a Workflow
 
 ```bash
-output workflow stop <workflowId>
+npx output workflow stop <workflowId>
 ```
 
 ### Safety Considerations
@@ -48,15 +48,15 @@ Before stopping, consider:
 
 ```bash
 # Check status - workflow has been running too long
-output workflow status abc123xyz
+npx output workflow status abc123xyz
 # Status: RUNNING (for 2 hours)
 
 # Decide to stop it
-output workflow stop abc123xyz
+npx output workflow stop abc123xyz
 # Workflow abc123xyz has been stopped
 
 # Verify it's terminated
-output workflow status abc123xyz
+npx output workflow status abc123xyz
 # Status: TERMINATED
 ```
 
@@ -64,26 +64,26 @@ output workflow status abc123xyz
 
 ```bash
 # Realized input was wrong immediately after starting
-output workflow start expensive-job '{"wrong": "input"}'
+npx output workflow start expensive-job '{"wrong": "input"}'
 # Workflow ID: job-abc123
 
 # Stop before it processes too much
-output workflow stop job-abc123
+npx output workflow stop job-abc123
 
 # Start again with correct input
-output workflow start expensive-job '{"correct": "input"}'
+npx output workflow start expensive-job '{"correct": "input"}'
 ```
 
 **Scenario**: Stop multiple workflows
 
 ```bash
 # Get list of running workflows
-output workflow runs list --format json | jq '.[] | select(.status == "RUNNING") | .workflowId'
+npx output workflow runs list --format json | jq '.[] | select(.status == "RUNNING") | .workflowId'
 
 # Stop each one (carefully review first!)
 for id in abc123 def456; do
   echo "Stopping $id"
-  output workflow stop $id
+  npx output workflow stop $id
 done
 ```
 
@@ -92,14 +92,14 @@ done
 ### Check the State
 
 ```bash
-output workflow status <workflowId>
+npx output workflow status <workflowId>
 # Status: TERMINATED
 ```
 
 ### Review What Happened
 
 ```bash
-output workflow debug <workflowId> --format json
+npx output workflow debug <workflowId> --format json
 ```
 
 This shows:
@@ -118,7 +118,7 @@ If the workflow made partial changes:
 
 ```bash
 # Start a fresh execution
-output workflow start <workflowName> '<input>'
+npx output workflow start <workflowName> '<input>'
 ```
 
 ## What Happens When You Stop
@@ -133,7 +133,7 @@ output workflow start <workflowName> '<input>'
 
 ### "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 already completed"
 - The workflow finished before the stop command
@@ -151,14 +151,14 @@ output workflow start <workflowName> '<input>'
 ## Best Practices
 
 1. **Always check status first**: Confirm the workflow is actually RUNNING
-2. **Review before stopping**: Use `output workflow debug` to understand state
+2. **Review before stopping**: Use `npx output workflow debug` to understand state
 3. **Document why**: Note why you stopped the workflow for future reference
 4. **Plan for cleanup**: Know what side effects may need manual handling
 5. **Consider alternatives**: Sometimes waiting is better than stopping
 
 ## Related Commands
 
-- `output workflow status <id>` - Check current status
-- `output workflow debug <id>` - Review execution details
-- `output workflow start <name>` - Start a new execution
-- `output workflow runs list` - View execution history
+- `npx output workflow status <id>` - Check current status
+- `npx output workflow debug <id>` - Review execution details
+- `npx output workflow start <name>` - Start a new execution
+- `npx output workflow runs list` - View execution history

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

@@ -25,12 +25,12 @@ This skill provides guidance on retrieving and analyzing workflow execution trac
 
 **Basic trace (text format, may be truncated):**
 ```bash
-output workflow debug <workflowId>
+npx output workflow debug <workflowId>
 ```
 
 **Full trace (JSON format, recommended for detailed analysis):**
 ```bash
-output workflow debug <workflowId> --format json
+npx output workflow debug <workflowId> --format json
 ```
 
 **Tip**: Always use `--format json` when you need complete trace data. The text format truncates long values which can hide important debugging information.
@@ -96,10 +96,10 @@ When examining JSON traces, focus on these fields:
 
 ```bash
 # Get the workflow ID from runs list
-output workflow runs list --limit 5 --format json
+npx output workflow runs list --limit 5 --format json
 
 # Get detailed trace
-output workflow debug abc123xyz --format json
+npx output workflow debug abc123xyz --format json
 
 # Look for the failing step in the output
 # Example output structure:
@@ -116,13 +116,13 @@ output workflow debug abc123xyz --format json
 **Scenario**: Investigate retry behavior
 
 ```bash
-output workflow debug abc123xyz --format json | jq '.steps[] | select(.attempts > 1)'
+npx output workflow debug abc123xyz --format json | jq '.steps[] | select(.attempts > 1)'
 ```
 
 **Scenario**: Check inputs to a specific step
 
 ```bash
-output workflow debug abc123xyz --format json | jq '.steps[] | select(.name == "processData") | .input'
+npx output workflow debug abc123xyz --format json | jq '.steps[] | select(.name == "processData") | .input'
 ```
 
 ## Next Steps After Analysis
@@ -130,5 +130,5 @@ output workflow debug abc123xyz --format json | jq '.steps[] | select(.name == "
 1. Match the error to common patterns (see error skills)
 2. Consult the `workflow-quality` subagent for best practices
 3. Make code fixes based on identified issues
-4. Re-run the workflow: `output workflow run <workflowName> <input>`
+4. Re-run the workflow: `npx output workflow run <workflowName> <input>`
 5. Verify the fix with a new trace

package/dist/templates/project/README.md.template

@@ -49,7 +49,7 @@ npx output workflow run simple --input '{"question": "who really is ada lovelace
 
 ### 5. Stop Services
 
-Press `Ctrl+C` in the terminal running `output dev` to stop all services gracefully.
+Press `Ctrl+C` in the terminal running `npm run dev` to stop all services gracefully.
 
 ### 6. View Logs
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@output.ai/cli",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "CLI for Output.ai workflow generation",
   "type": "module",
   "main": "dist/index.js",
@@ -35,7 +35,7 @@
     "handlebars": "4.7.8",
     "json-schema-library": "10.3.0",
     "ky": "1.12.0",
-    "validator": "13.15.20"
+    "validator": "13.15.22"
   },
   "devDependencies": {
     "@types/cli-progress": "3.11.6",

package/dist/templates/workflow/.env.template

@@ -1,7 +0,0 @@
-# API Keys for LLM providers
-OPENAI_API_KEY=your_openai_api_key_here
-ANTHROPIC_API_KEY=your_anthropic_api_key_here
-
-# Optional: Additional configuration
-# NODE_ENV=development
-# LOG_LEVEL=info