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 Start

by growthxai in growthxai/output

Start an Output SDK workflow asynchronously without waiting for completion.

Apache-2.0Auto-check: notes

Install Output Workflow Start

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

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

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

At a glance

Start an Output SDK workflow asynchronously without waiting for completion.

  • Works in 2 steps: Inline JSON → File Path (Recommended)
  • Starting long-running workflows
  • SKILL.md covers Overview, When to Use This Skill, When to Use Sync Instead and Instructions, plus 5 more sections
  • Calls npx

What it does

Output Workflow Start is an agent skill from growthxai/output. Start an Output SDK workflow asynchronously without waiting for completion. Use when starting long-running workflows, getting a workflow ID for later monitoring, running workflows in the background, or executing multiple workflows in parallel.

Its SKILL.md is about 1.9k 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

  • Starting long-running workflows
  • Getting a workflow ID for later monitoring
  • Running workflows in the background
  • Executing multiple workflows in parallel

Example prompts

  • “/output-workflow-start”

Requirements

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

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Inline JSON
  2. File Path (Recommended)

What it can do on your machine

Read from SKILL.md and the folder at commit ff9e1ab. 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
    • Read
    • Write

    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 Start loads about 1.9k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 670 words of instructions outside code blocks.

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

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, Read, Write

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 ff9e1ab, republished under its Apache-2.0 licence (© growthxai). 670 words, ~1,945 tokens.

Download SKILL.mdSave it as .claude/skills/output-workflow-start/SKILL.md (or your agent's skills folder).
name
output-workflow-start
description
Start an Output SDK workflow asynchronously without waiting for completion. Use when starting long-running workflows, getting a workflow ID for later monitoring, running workflows in the background, or executing multiple workflows in parallel.
allowed-tools
Bash, Read, Write

Start Workflow Asynchronously

Overview

This skill starts a workflow asynchronously, meaning the command returns immediately with a workflow ID while the workflow executes in the background. Use this for long-running workflows or when you need to run multiple workflows in parallel.

When to Use This Skill

  • Starting workflows that take minutes or hours
  • Running multiple workflows in parallel
  • When you need to disconnect and check results later
  • Monitoring workflow progress separately
  • When you need the workflow ID immediately for tracking

When to Use Sync Instead

Consider using npx output workflow run (sync) when:

  • Workflow completes quickly (seconds)
  • You need the result immediately in your terminal
  • Simple testing during development
  • You want a single command with the result

Instructions

Basic Syntax
bash
npx output workflow start <workflowName> --input '<json-input>'
npx output workflow start <workflowName> --input <path-to-json-file>

The --input flag is required when the workflow expects input data.

Input Methods
1. Inline JSON

Pass JSON directly on the command line:

bash
npx output workflow start data-migration --input '{"batchSize": 1000}'

Reference a JSON file containing the input:

bash
npx output workflow start data-migration --input src/data_migration/scenarios/large_batch.json

This is the recommended approach because:

  • Input is version controlled and reproducible
  • Complex inputs are easier to read and edit
  • Scenarios can be shared and reused
Getting the Workflow ID

The command outputs the workflow ID which you'll need for:

  • Checking status: npx output workflow status <id>
  • Getting results: npx output workflow result <id>
  • Debugging: npx output workflow debug <id>
Start and Watch in One Command

Add --monitor (-m) to attach immediately after starting and stream step updates until the workflow ends, instead of polling workflow status:

bash
npx output workflow start data-migration --input src/data_migration/scenarios/large_batch.json --monitor

This attaches to the exact run that was just started. Ctrl+C detaches without stopping the workflow (exit 130), and the command exits 1 if the workflow fails. If monitoring itself drops (an API restart, a reset connection), the workflow keeps running and the command exits 3 instead — so a retry keyed on a failed workflow can't re-submit one that is already in flight.

Monitoring reports progress, not the return value; the command closes by naming the follow-up — npx output workflow result <id> after a run that completed, npx output workflow debug <id> after one that failed.

These flags tune the stream and require --monitor:

FlagDefaultDescription
--interval2500Poll interval in milliseconds
--include-payloadsfalseInclude decoded step input/output payloads
--colortrueColorize status output (--no-color to disable)

--monitor cannot be combined with --json. Under --json the CLI suppresses progress output and prints one JSON object at the end, so the stream would be silently swallowed and the command would look hung until the workflow finished. To get JSON, either use npx output workflow run --json (wait for the result), or start without --monitor and attach with npx output workflow monitor <id> --format json (streaming NDJSON).

Prefer --monitor over a workflow status polling loop when you're watching a single workflow through to completion. Keep the plain async form when starting several workflows in parallel, since --monitor blocks until the run ends.

Show full SKILL.md (198 more words)Show less

Examples

Scenario: Start a long-running workflow with scenario file

bash
npx output workflow start data-migration --input src/data_migration/scenarios/full_migration.json

# Output:
# Started workflow: data-migration
# Workflow ID: abc123xyz
# Use 'npx output workflow status abc123xyz' to check progress

Scenario: Start multiple workflows in parallel using scenario files

bash
# Start several workflows with different scenario files
npx output workflow start process-batch --input src/process_batch/scenarios/batch_1.json
npx output workflow start process-batch --input src/process_batch/scenarios/batch_2.json
npx output workflow start process-batch --input src/process_batch/scenarios/batch_3.json

# Note: Save the workflow IDs to check them later

Scenario: Create scenario then start workflow

bash
# Create a scenario file
mkdir -p src/generate_report/scenarios
cat > src/generate_report/scenarios/annual_2024.json << 'EOF'
{
  "year": 2024,
  "includeCharts": true,
  "format": "pdf"
}
EOF

# Start the workflow
npx output workflow start generate-report --input src/generate_report/scenarios/annual_2024.json
# Output: Workflow ID: report-2024-abc

# Check status periodically
npx output workflow status report-2024-abc
# Output: Status: RUNNING

# Later, check again
npx output workflow status report-2024-abc
# Output: Status: COMPLETED

# Get the result
npx output workflow result report-2024-abc

Scenario: Quick inline test for development

bash
npx output workflow start quick-job --input '{"test": true}'

Scenario: Script for parallel execution

bash
# Start workflows and capture IDs
ID1=$(npx output workflow start job --input src/job/scenarios/type_a.json | grep "Workflow ID" | cut -d: -f2 | tr -d ' ')
ID2=$(npx output workflow start job --input src/job/scenarios/type_b.json | grep "Workflow ID" | cut -d: -f2 | tr -d ' ')

# Wait and check results
npx output workflow result $ID1
npx output workflow result $ID2

Following Up After Starting

Check Status
bash
npx output workflow status <workflowId>

Status values:

  • RUNNING: Still executing
  • COMPLETED: Finished successfully
  • FAILED: Encountered an error
  • TERMINATED: Was manually stopped
Get Result
bash
npx output workflow result <workflowId>

Only works for COMPLETED workflows. For FAILED workflows, use debug.

Debug If Failed
bash
npx output workflow debug <workflowId> --json
Stop If Needed
bash
npx output workflow stop <workflowId>

Workflow ID Management

When starting multiple workflows, keep track of IDs:

bash
# Log IDs to a file
npx output workflow start batch-job --input src/batch_job/scenarios/id_1.json >> workflow-ids.txt
npx output workflow start batch-job --input src/batch_job/scenarios/id_2.json >> workflow-ids.txt

# Or use a naming convention in your workflow that makes IDs predictable

Best Practices

  1. Use scenario files: Store inputs in src/<workflow>/scenarios/ for reproducibility
  2. Save the workflow ID: Always note the ID for later reference
  3. Monitor long workflows: Use npx output workflow status to check progress
  4. Handle failures: Check status before getting results
  5. Clean up: Stop any stuck workflows with npx output workflow stop
  • npx output workflow run <name> --input - Execute synchronously
  • npx output workflow monitor <id> - Attach to a run already in progress
  • npx output workflow status <id> - Check execution status
  • npx output workflow result <id> - Get execution result
  • npx output workflow stop <id> - Stop a running workflow
  • npx output workflow debug <id> - Debug a workflow execution

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

Open the folder on GitHubat commit ff9e1ab

Compare with similar skills

Output Workflow Start 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 Start compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Workflow Start this skillgrowthxai/output442—~1.9kAutomated safety check: NotesApache-2.0
Verification Before Completionforyourhealth111-pixel/Vibe-Skills3.6k—~1.1kAutomated safety check: PassApache-2.0
Verification Before Completionfarm-fe/farm5.6k46 repos~1kAutomated safety check: PassMIT
Verification Before CompletionjnMetaCode/superpowers-zh8.3k—~443Automated safety check: PassMIT
Complete Partial PRpydantic/pydantic-ai20k—~2.4kAutomated safety check: PassMIT
Deliverable CompletionHKUDS/OpenSpace7.8k—~731Automated safety check: PassMIT

Similar skills

  • Verification Before Completion

    foryourhealth111-pixel/Vibe-Skills

    Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.

    3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Verification Before Completion

    farm-fe/farm

    A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…

    5.6k GitHub starsUsed in 46 repos~1k tokens
    Agent WorkflowsAuto-check passed

  • Verification Before Completion

    jnMetaCode/superpowers-zh

    Chinese-language rule that bars an agent from claiming work is done, fixed or passing until it has run a verification command and read the output.

    8.3k GitHub stars~443 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Complete Partial PR

    pydantic/pydantic-ai

    Official

    Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point.

    20k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Deliverable Completion

    HKUDS/OpenSpace

    Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required

    7.8k GitHub stars~731 tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

  • Scout Completion

    kunchenguid/firstmate

    Load when a scout reports completion, presents a visual artifact for iteration, or is being considered for promotion to implementation.

    7.7k GitHub stars~349 tokensUpdated yesterday
    Auto-check passed

More from growthxai/output

All 52 skills in this repo

  • LLM Output Schema Constraints

    growthxai/output

    Zod schema constraints that Anthropic rejects or silently ignores when sent as structured-output tool definitions via aiSdk.Output.object().

    442 GitHub stars~597 tokensUpdated yesterday
    Auto-check passed

  • 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

Questions about Output Workflow Start

What does Output Workflow Start do?

Start an Output SDK workflow asynchronously without waiting for completion. Output Workflow Start is an agent skill from growthxai/output. Start an Output SDK workflow asynchronously without waiting for completion.

When should I use Output Workflow Start?

Output Workflow Start fits situations like: starting long-running workflows; getting a workflow ID for later monitoring; running workflows in the background; executing multiple workflows in parallel.

How do I install Output Workflow Start in Claude Code?

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

How do I install Output Workflow Start in Codex?

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

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

What does Output Workflow Start need to run?

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

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

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

About 1.9k tokens (SKILL.md is roughly 7.8k 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 Start?

Skills that share tags, products or a category with Output Workflow Start: Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Verification Before Completion (farm-fe/farm, 5.6k stars), Verification Before Completion (jnMetaCode/superpowers-zh, 8.3k stars) and Complete Partial PR (pydantic/pydantic-ai, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Workflow Start?

growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 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.