Agent skill

Output Workflow Runs List

by growthxai in growthxai/output

List Output SDK workflow execution history. An agent skill from growthxai/output.

Apache-2.0Auto-check: notesDevelopment

Install Output Workflow Runs List

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

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

GitHub CLI
$ gh skill install growthxai/output output-workflow-runs-list --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-runs-list .claude/skills/output-workflow-runs-list && 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-runs-list
GitHub stars
442
Token cost
~1k tokens
SKILL.md length
378 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

List Output SDK workflow execution history. An agent skill from growthxai/output.

  • Works in 4 steps: Multiple FAILED runs: Indicates a… → Mix of COMPLETED and FAILED: Could be… → All recent runs TERMINATED: Someone may… → …
  • Finding failed runs
  • SKILL.md covers Overview, When to Use This Skill, Instructions and Understanding the Output, plus 3 more sections
  • Calls npx and jq

What it does

Output Workflow Runs List is an agent skill from growthxai/output. List Output SDK workflow execution history. Use when finding failed runs, reviewing past executions, identifying workflow IDs for debugging, filtering runs by workflow type, or investigating recent workflow activity.

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

It sits in Development, covering Debugging. 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

  • Finding failed runs
  • Reviewing past executions
  • Identifying workflow IDs for debugging
  • Filtering runs by workflow type

Example prompts

  • “/output-workflow-runs-list”

Requirements

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

Workflow steps

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

  1. Multiple FAILED runs: Indicates a persistent bug
  2. Mix of COMPLETED and FAILED: Could be input-dependent issues
  3. All recent runs TERMINATED: Someone may be stopping workflows
  4. Long RUNNING times: Possible hang or performance issue

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
    • jq

    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 Runs List loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 378 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~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). 378 words, ~1,036 tokens.

Download SKILL.mdSave it as .claude/skills/output-workflow-runs-list/SKILL.md (or your agent's skills folder).
name
output-workflow-runs-list
description
List Output SDK workflow execution history. Use when finding failed runs, reviewing past executions, identifying workflow IDs for debugging, filtering runs by workflow type, or investigating recent workflow activity.
allowed-tools
Bash

List Workflow Execution History

Overview

This skill helps you view the execution history of workflows. Use it to find failed runs, identify workflow IDs for debugging, and review past executions.

When to Use This Skill

  • Finding recent failed workflow runs
  • Getting a workflow ID for debugging
  • Reviewing execution history for a specific workflow
  • Investigating when a problem started occurring
  • Checking the status of recent executions

Instructions

List All Recent Runs
bash
npx output workflow runs list

By default, this shows the 100 most recent workflow executions across all workflow types.

Available Flags
FlagDescriptionDefault
--limit <n>Number of runs to display100
--format <type>Output format: table, texttable
--jsonOutput machine-readable JSONfalse
Filter by Workflow Name
bash
npx output workflow runs list <workflowName>

This shows only runs for the specified workflow type.

Get Detailed JSON Output
bash
npx output workflow runs list --json

Use JSON format for programmatic analysis or when you need full details.

Understanding the Output

Status Values
StatusMeaningAction
RUNNINGWorkflow is currently executingWait or monitor
COMPLETEDWorkflow finished successfullyNo action needed
FAILEDWorkflow encountered an errorDebug with trace
TERMINATEDWorkflow was manually stoppedReview if expected
TIMED_OUTWorkflow exceeded time limitCheck for long operations
Key Fields

When viewing runs, pay attention to:

  • Workflow ID: Unique identifier needed for debugging commands
  • Status: Current execution state
  • Start Time: When the execution began
  • End Time: When the execution completed (if finished)
  • Workflow Name: The type of workflow that ran
Show full SKILL.md (150 more words)Show less

Examples

Scenario: Find failed workflow runs

bash
# List recent runs and look for FAILED status
npx output workflow runs list --limit 20

# Or use JSON format with jq to filter
npx output workflow runs list --json | jq '.[] | select(.status == "FAILED")'

Scenario: Get workflow ID for debugging

bash
# List runs for a specific workflow
npx output workflow runs list my-workflow --limit 5

# Note the workflow ID from the output (e.g., "abc123xyz")
# Then debug it
npx output workflow debug abc123xyz --json

Scenario: Review recent activity for a specific workflow

bash
# See the last 10 runs of the data-pipeline workflow
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
npx output workflow runs list --json > workflow-runs.json

Scenario: Find when failures started

bash
# Look at more history to find patterns
npx output workflow runs list --limit 50 --json | jq 'group_by(.status) | map({status: .[0].status, count: length})'

Identifying Problems

Signs of Issues
  1. Multiple FAILED runs: Indicates a persistent bug
  2. Mix of COMPLETED and FAILED: Could be input-dependent issues
  3. All recent runs TERMINATED: Someone may be stopping workflows
  4. Long RUNNING times: Possible hang or performance issue
Next Steps After Finding a Failed Run
  1. Copy the workflow ID from the run
  2. Get the execution trace: npx output workflow debug <workflowId> --json
  3. Analyze the trace to identify the failure
  4. Apply the appropriate fix based on the error pattern
  • 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

© 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-runs-list of growthxai/output.

Open the folder on GitHubat commit 99ee298

Compare with similar skills

Output Workflow Runs List next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Output Workflow Runs List compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Workflow Runs List this skillgrowthxai/output442—~1kAutomated safety check: NotesApache-2.0
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 52 repos~2.4k tokens
    DevelopmentAuto-check passed

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
  • 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

Categories

Questions about Output Workflow Runs List

What does Output Workflow Runs List do?

List Output SDK workflow execution history. An agent skill from growthxai/output. Output Workflow Runs List is an agent skill from growthxai/output. List Output SDK workflow execution history.

When should I use Output Workflow Runs List?

Output Workflow Runs List fits situations like: finding failed runs; reviewing past executions; identifying workflow IDs for debugging; filtering runs by workflow type.

How do I install Output Workflow Runs List in Claude Code?

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

How do I install Output Workflow Runs List in Codex?

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

Can I use Output Workflow Runs List 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-runs-list -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-runs-list, .gemini/skills/output-workflow-runs-list, .github/skills/output-workflow-runs-list and .opencode/skills/output-workflow-runs-list in your project.

What does Output Workflow Runs List need to run?

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

Does Output Workflow Runs List 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 Runs List 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 Runs List use?

Output Workflow Runs List 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 Runs List use?

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

What are the alternatives to Output Workflow Runs List?

Skills that share tags, products or a category with Output Workflow Runs List: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Workflow Runs List?

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.