Install any skill in seconds. Free to start, no credit card required.
Get Started Free →List all available Output SDK workflows in the project. Use when discovering what workflows exist, checking workflow names, exploring the project's workflow structure, or when unsure which workflows are available to run.
.claude/skills/growthxai-output-workflow-list/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 14% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -27% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 131% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -9% | 0% |
This skill helps you discover all available workflows in an Output SDK project. Workflows are the main execution units that orchestrate steps to accomplish tasks.
bashnpx output workflow list
This command scans the project and displays all available workflows.
The command outputs a table with workflow information:
| Column | Description | |--------|-------------| | Name | The workflow identifier used in commands | | Description | Brief description of what the workflow does | | Location | File path where the workflow is defined |
Workflows are typically located in:
src/workflows/*/Each workflow directory usually contains:
workflow.ts or index.ts - The main workflow definitionAfter finding a workflow, you can examine its code:
bash# Read the workflow file cat src/workflows/<workflowName>/workflow.ts # Or examine the entire workflow directory ls -la src/workflows/<workflowName>/
Scenario: Discover available workflows in a project
bashnpx output workflow list # Example output: # Name Description Location # ----------- --------------------------- -------------------------------- # simple Simple workflow example src/workflows/simple/workflow.ts # data-pipeline Process and transform data src/workflows/data-pipeline/workflow.ts # user-signup Handle user registration src/workflows/user-signup/workflow.ts
Scenario: Verify a workflow exists before running
bash# Check if "email-sender" workflow exists npx output workflow list | grep email-sender # If no output, the workflow doesn't exist # If found, proceed with running it npx output workflow run email-sender --input '{"to": "user@example.com"}'
Scenario: Explore workflow implementation
bash# List workflows npx output workflow list # Find the location and examine it cat src/workflows/simple/workflow.ts
src/workflows/*/npm run output:worker:build to check for TypeScript errorsnpx output workflow run <name> - Execute a workflow synchronouslynpx output workflow start <name> - Start a workflow asynchronouslynpx output workflow runs list - View execution history| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 7,996 | 3,687 | -54% | 1 | 1 | 0% | 1,093 | 1,243 | +14% | 0 | 0 | — |
case-02 | fail→pass | 9,494 | 2,345 | -75% | 1 | 1 | 0% | 1,328 | 970 | -27% | 0 | 0 | — |
case-03 | fail→pass | 2,602 | 1,262 | -51% | 1 | 1 | 0% | 343 | 794 | +131% | 0 | 0 | — |
case-04 | fail→pass | 11,629 | 4,534 | -61% | 1 | 1 | 0% | 1,919 | 1,511 | -21% | 0 | 0 | — |
case-05 | fail→pass | 8,029 | 2,942 | -63% | 1 | 1 | 0% | 1,265 | 1,155 | -9% | 0 | 0 | — |
case-06 | pass→pass | 9,946 | 2,450 | -75% | 1 | 1 | 0% | 1,677 | 1,048 | -38% | 0 | 0 | — |
case-07 | fail→pass | 13,342 | 3,177 | -76% | 1 | 1 | 0% | 2,222 | 1,174 | -47% | 0 | 0 | — |
case-08 | fail→pass | 10,063 | 4,066 | -60% | 1 | 1 | 0% | 1,463 | 1,385 | -5% | 0 | 0 | — |
case-09 | fail→pass | 11,658 | 3,684 | -68% | 1 | 1 | 0% | 1,862 | 1,210 | -35% | 0 | 0 | — |
case-10 | fail→pass | 9,892 | 3,620 | -63% | 1 | 1 | 0% | 1,660 | 1,273 | -23% | 0 | 0 | — |
case-11 | fail→pass | 9,003 | 1,995 | -78% | 1 | 1 | 0% | 1,309 | 975 | -26% | 0 | 0 | — |
case-12 | fail→pass | 6,431 | 3,110 | -52% | 1 | 1 | 0% | 1,046 | 1,132 | +8% | 0 | 0 | — |
case-13 | pass→pass | 3,811 | 2,181 | -43% | 1 | 1 | 0% | 611 | 1,002 | +64% | 0 | 0 | — |
case-14 | fail→pass | 7,429 | 2,617 | -65% | 1 | 1 | 0% | 1,096 | 1,062 | -3% | 0 | 0 | — |
case-15 | fail→pass | 14,509 | 2,211 | -85% | 1 | 1 | 0% | 2,237 | 1,045 | -53% | 0 | 0 | — |
case-16 | fail→pass | 18,393 | 2,961 | -84% | 1 | 1 | 0% | 2,747 | 1,108 | -60% | 0 | 0 | — |
case-17 | pass→pass | 13,858 | 5,659 | -59% | 1 | 1 | 0% | 2,066 | 1,421 | -31% | 0 | 0 | — |
case-18 | fail→pass | 19,902 | 1,626 | -92% | 1 | 1 | 0% | 3,031 | 878 | -71% | 0 | 0 | — |
case-19 | pass→pass | 13,602 | 1,728 | -87% | 1 | 1 | 0% | 1,994 | 887 | -56% | 0 | 0 | — |
case-20 | pass→pass | 6,627 | 2,966 | -55% | 1 | 1 | 0% | 1,018 | 1,131 | +11% | 0 | 0 | — |
case-21 | fail→pass | 9,483 | 3,275 | -65% | 1 | 1 | 0% | 1,635 | 1,208 | -26% | 0 | 0 | — |
case-22 | fail→fail | 18,405 | 3,286 | -82% | 1 | 1 | 0% | 2,869 | 1,218 | -58% | 0 | 0 | — |
case-23 | fail→fail | 9,560 | 2,455 | -74% | 1 | 1 | 0% | 1,482 | 1,033 | -30% | 0 | 0 | — |
case-24 | fail→pass | 8,059 | 2,948 | -63% | 1 | 1 | 0% | 1,178 | 1,107 | -6% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 24 cases were attempted. The headline lift of +71 percentage points is the difference between those two pass rates over the 24 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.