New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Output Workflow Status

by growthxai in growthxai/output

Check the status of an Output SDK workflow execution. An agent skill from growthxai/output.

Apache-2.0Auto-check: notes

Install Output Workflow Status

skills CLI
$ npx skills add growthxai/output --skill output-workflow-status -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install growthxai/output output-workflow-status --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-workflow-status .claude/skills/output-workflow-status && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
output-workflow-status
GitHub stars
442
Token cost
~1.1k tokens
SKILL.md length
372 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Check the status of an Output SDK workflow execution. An agent skill from growthxai/output.

  • Works in 3 steps: Check if the workflow is stuck: npx… → Look for infinite loops or waiting… → Consider stopping: npx output workflow…
  • Monitoring a running workflow
  • SKILL.md covers Overview, When to Use This Skill, When to Use Other Commands and Instructions, plus 6 more sections
  • Calls npx

What it does

Output Workflow Status is an agent skill from growthxai/output. Check the status of an Output SDK workflow execution. Use when monitoring a running workflow, checking if a workflow completed, or determining workflow state (RUNNING, COMPLETED, FAILED, TERMINATED).

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already… The licence is Apache-2.0.

When your agent uses it

  • Monitoring a running workflow
  • Checking if a workflow completed
  • Determining workflow state (RUNNING

Example prompts

  • “/output-workflow-status”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Bash

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Check if the workflow is stuck: npx output workflow debug
  2. Look for infinite loops or waiting operations
  3. Consider stopping: npx output workflow stop

What it can do on your machine

Read from SKILL.md and the folder at commit 99ee298. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Output Workflow Status loads about 1.1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 372 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from growthxai/output at commit 99ee298, republished under its Apache-2.0 licence (© growthxai). 372 words, ~1,094 tokens.

Download SKILL.mdSave it as .claude/skills/output-workflow-status/SKILL.md (or your agent's skills folder).
name
output-workflow-status
description
Check the status of an Output SDK workflow execution. Use when monitoring a running workflow, checking if a workflow completed, or determining workflow state (RUNNING, COMPLETED, FAILED, TERMINATED).
allowed-tools
Bash

Check Workflow Execution Status

Overview

This skill checks the current execution status of a workflow. Use it to monitor running workflows, verify completion, or determine if a workflow failed before attempting to get its result.

When to Use This Skill

  • Monitoring a workflow started asynchronously
  • Checking if a workflow has completed
  • Determining why you can't get a workflow result
  • Verifying workflow state before taking action
  • Polling for completion in scripts

When to Use Other Commands

  • 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
npx output workflow status <workflowId>

Replace <workflowId> with the ID from npx output workflow start or npx output workflow runs list.

Understanding Status Values

StatusMeaningNext Action
RUNNINGWorkflow is currently executingWait and check again
COMPLETEDWorkflow finished successfullyGet result with npx output workflow result
FAILEDWorkflow encountered an errorDebug with npx output workflow debug
TERMINATEDWorkflow was manually stoppedReview if expected, restart if needed
TIMED_OUTWorkflow exceeded time limitCheck for long operations, adjust timeout

Examples

Scenario: Monitor a running workflow

bash
# Start a workflow
npx output workflow start data-sync --input '{"source": "external"}'
# Output: Workflow ID: sync-abc123

# Check status
npx output workflow status sync-abc123
# Output: Status: RUNNING

# Wait and check again
sleep 30
npx output workflow status sync-abc123
# Output: Status: COMPLETED

Scenario: Poll for completion in a script

bash
WORKFLOW_ID="abc123xyz"

while true; do
  STATUS=$(npx output workflow status $WORKFLOW_ID)
  echo "Current status: $STATUS"

  if [[ "$STATUS" == *"COMPLETED"* ]]; then
    echo "Workflow completed!"
    npx output workflow result $WORKFLOW_ID
    break
  elif [[ "$STATUS" == *"FAILED"* ]]; then
    echo "Workflow failed!"
    npx output workflow debug $WORKFLOW_ID --json
    break
  fi

  sleep 10
done

Scenario: Check before getting result

bash
# Verify status first
npx output workflow status my-workflow-123

# If COMPLETED, get result
npx output workflow result my-workflow-123

# If FAILED, debug instead
npx output workflow debug my-workflow-123 --json

Scenario: Batch status check

bash
# Check multiple workflows
for id in abc123 def456 ghi789; do
  echo "Workflow $id: $(npx output workflow status $id)"
done

Status Transitions

Workflows typically follow these paths:

RUNNING -> COMPLETED (success)
RUNNING -> FAILED (error occurred)
RUNNING -> TERMINATED (manually stopped)
RUNNING -> TIMED_OUT (exceeded limit)
Show full SKILL.md (157 more words)Show less

Interpreting Status Output

The status command returns information including:

  • Status: Current state (RUNNING, COMPLETED, FAILED, etc.)
  • Duration: How long the workflow has been running or ran
  • Start Time: When the workflow began

Troubleshooting

"Workflow not found"
  • The workflow ID may be incorrect
  • The workflow may have been deleted from history
  • Check npx output workflow runs list to find the correct ID
Status stays RUNNING too long
  1. Check if the workflow is stuck: npx output workflow debug <id>
  2. Look for infinite loops or waiting operations
  3. Consider stopping: npx output workflow stop <id>
Unexpected TERMINATED status
  • Someone may have manually stopped the workflow
  • Check with npx output workflow debug for context
  • Restart if needed: npx output workflow start
  • 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

© growthxai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-workflow-status of growthxai/output.

Open the folder on GitHubat commit 99ee298

More from growthxai/output

All 50 skills in this repo

  • Output Build Workflow

    growthxai/output

    Implement an Output SDK workflow from a plan document. An agent skill from growthxai/output.

    442 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Output Credentials Edit

    growthxai/output

    View, edit, and set encrypted credentials in an Output.ai project.

    442 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes

  • Output Credentials Env Vars

    growthxai/output

    Wire encrypted credentials to environment variables using the credential: convention.

    442 GitHub stars~930 tokensUpdated yesterday
    Auto-check: notes

  • Output Credentials Init

    growthxai/output

    Initialize encrypted credentials for an Output.ai project. An agent skill from growthxai/output.

    442 GitHub stars~803 tokensUpdated yesterday
    Auto-check: notes

  • Output Debug Workflow

    growthxai/output

    Debug Output SDK workflow issues. An agent skill from growthxai/output.

    442 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Output Dev Agent Class

    growthxai/output

    Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.

    442 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Questions about Output Workflow Status

What does Output Workflow Status do?

Check the status of an Output SDK workflow execution. An agent skill from growthxai/output. Output Workflow Status is an agent skill from growthxai/output. Check the status of an Output SDK workflow execution.

When should I use Output Workflow Status?

Output Workflow Status fits situations like: monitoring a running workflow; checking if a workflow completed; determining workflow state (RUNNING.

How do I install Output Workflow Status in Claude Code?

Run `npx skills add growthxai/output --skill output-workflow-status -a claude-code`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-workflow-status in growthxai/output) into .claude/skills/output-workflow-status in your project. Claude Code loads it when a task matches its description.

How do I install Output Workflow Status in Codex?

Run `npx skills add growthxai/output --skill output-workflow-status -a codex`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-workflow-status in growthxai/output) into .agents/skills/output-workflow-status in your project. Codex loads it when a task matches its description.

Can I use Output Workflow Status in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthxai/output --skill output-workflow-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/output-workflow-status, .gemini/skills/output-workflow-status, .github/skills/output-workflow-status and .opencode/skills/output-workflow-status in your project.

What does Output Workflow Status need to run?

Going by SKILL.md and its folder, Output Workflow Status needs the command-line tools its instructions call (npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash.

Does Output Workflow Status access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Output Workflow Status safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Output Workflow Status use?

Output Workflow Status is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Output Workflow Status use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

Who maintains Output Workflow Status?

growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.

Source: growthxai/output on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.