From outputai
Retrieves JSON results from completed Output SDK workflows using `npx output workflow result <id>`. Use after async starts and status checks to process returns, script outputs, compare runs, or pipe to jq.
npx claudepluginhub growthxai/output --plugin outputaiThis skill is limited to using the following tools:
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.
Checks Output SDK workflow status (RUNNING, COMPLETED, FAILED, TERMINATED). Use for monitoring async executions, verifying completion before results, polling in scripts, or handling failures.
Creates durable, resumable workflows using Vercel's Workflow SDK. Use for surviving restarts, pausing on external events, retrying failures, or coordinating multi-step operations over time.
Provides expert guidance on Vercel Workflow DevKit for durable workflows, long-running tasks, API routes, agents with pause/resume, retries, step execution, crash-safe orchestration.
Share bugs, ideas, or general feedback.
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.
npx output workflow debug insteadnpx output workflow result <workflowId>
The result is the return value of the workflow function, typically JSON.
Before getting results, verify the workflow completed:
npx output workflow status <workflowId>
# Should show: COMPLETED
npx output workflow result <workflowId>
A successful workflow returns the value from its fn function:
// Workflow code
export default workflow({
fn: async (input) => {
return { processed: true, count: 42 };
}
});
# Result output
npx output workflow result abc123
# { "processed": true, "count": 42 }
If you try to get the result of a failed workflow:
npx output workflow debug instead to see what went wrongSome workflows don't return a value:
npx output workflow result abc123
# null
Scenario: Get result after async start
# Start workflow
npx output workflow start calculate '{"values": [1, 2, 3]}'
# Output: Workflow ID: calc-abc123
# Wait for completion
npx output workflow status calc-abc123
# Status: COMPLETED
# Get the result
npx output workflow result calc-abc123
# { "sum": 6, "average": 2 }
Scenario: Process result with jq
# Extract specific field
npx output workflow result abc123 | jq '.total'
# Format for display
npx output workflow result abc123 | jq '.'
# Save to file
npx output workflow result abc123 > result.json
Scenario: Compare results between runs
# Get results from two runs
npx output workflow result run-1-abc > result1.json
npx output workflow result run-2-xyz > result2.json
# Compare
diff result1.json result2.json
Scenario: Use in a script
WORKFLOW_ID="abc123"
# Wait for completion
while [[ $(npx output workflow status $WORKFLOW_ID) == *"RUNNING"* ]]; do
sleep 5
done
# Check if completed successfully
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"
npx output workflow debug $WORKFLOW_ID
fi
npx output workflow result abc123
# { "key": "value", "nested": { "data": true } }
npx output workflow result abc123
# [1, 2, 3, 4, 5]
npx output workflow result abc123
# 42
npx output workflow result abc123
# "success"
npx output workflow result abc123
# true
For large results, redirect to a file:
npx output workflow result abc123 > large-result.json
npx output workflow runs list to find valid IDsnpx output workflow status <id>npx output workflow debugnpx output workflow status <id> - Check if workflow completednpx output workflow debug <id> - Debug failed workflowsnpx output workflow run <name> - Run and get result in one stepnpx output workflow runs list - Find workflow IDs