Get the result of an Output SDK workflow execution. Use when retrieving the output of a completed workflow, getting the return value, or checking what a workflow produced after async execution.
Retrieves the return value of a completed Output SDK workflow using its workflow ID. Use this after async workflow execution to get results, process output with jq, or compare runs.
/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 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 IDsThis 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.