Agent skill

Output Dev Scenario File

by growthxai in growthxai/output

Create test scenario JSON files for Output SDK workflows. An agent skill from growthxai/output.

Apache-2.0Auto-check passedTesting & QA

Install Output Dev Scenario File

skills CLI
$ npx skills add growthxai/output --skill output-dev-scenario-file -a claude-code

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

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

At a glance

Create test scenario JSON files for Output SDK workflows. An agent skill from growthxai/output.

  • Works in 9 steps: Basic/Happy Path → Complete/Full-Featured → Edge Cases → …
  • Creating test inputs
  • SKILL.md covers Overview, When to Use This Skill, Location Convention and File Naming Convention, plus 9 more sections
  • Calls npx and jq; reaches github.com

What it does

Output Dev Scenario File is an agent skill from growthxai/output. Create test scenario JSON files for Output SDK workflows. Use when creating test inputs, documenting expected behaviors, or setting up workflow testing.

Its SKILL.md is about 2.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 Testing & QA. 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

  • Creating test inputs
  • Documenting expected behaviors
  • Setting up workflow testing

Example prompts

  • “/output-dev-scenario-file”

Requirements

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

Workflow steps

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

  1. Basic/Happy Path
  2. Complete/Full-Featured
  3. Edge Cases
  4. Error Cases (for validation testing)
  5. Document the Purpose
  6. Use Realistic Data
  7. Cover All Enum Values
  8. Include Optional Field Variations
  9. Create Regression Test Scenarios

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:

    • Read
    • Write
    • Edit

    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

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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 Dev Scenario File loads about 2.1k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 376 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~2.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 passed

The automated check found no risky patterns in SKILL.md.

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). 376 words, ~2,128 tokens.

Download SKILL.mdSave it as .claude/skills/output-dev-scenario-file/SKILL.md (or your agent's skills folder).
name
output-dev-scenario-file
description
Create test scenario JSON files for Output SDK workflows. Use when creating test inputs, documenting expected behaviors, or setting up workflow testing.
allowed-tools
Read, Write, Edit

Creating Scenario Files

Overview

This skill documents how to create test scenario JSON files for Output SDK workflows. Scenarios provide predefined inputs for testing workflows during development and validation.

When to Use This Skill

  • Creating test inputs for a new workflow
  • Documenting different use cases
  • Setting up regression tests
  • Debugging workflow behavior with specific inputs

Location Convention

Scenario files are stored INSIDE the workflow folder:

src/workflows/{workflow-name}/
├── workflow.ts
├── steps.ts
├── types.ts
└── scenarios/
    ├── basic_input.json
    ├── complex_input.json
    └── edge_case_empty.json

Important: Scenarios are workflow-specific and live inside the workflow folder.

File Naming Convention

Use snake_case for scenario file names:

{description}_input.json

Examples:

  • basic_input.json
  • test_input_solar_panels.json
  • edge_case_empty_content.json
  • complex_with_references.json

Naming patterns:

  • basic_* - Minimal valid input
  • complex_* - Full-featured input with all options
  • edge_case_* - Boundary conditions and edge cases
  • error_* - Inputs expected to produce errors

Basic Structure

A scenario file is a JSON file that matches the workflow's inputSchema:

json
{
  "fieldName": "value",
  "optionalField": "optional value",
  "numericField": 42,
  "arrayField": ["item1", "item2"]
}

Matching inputSchema

The scenario JSON must match the Zod schema defined in types.ts:

Example Schema (types.ts)
typescript
export const WorkflowInputSchema = z.object({
  content: z.string().describe('Text content to process'),
  numberOfIdeas: z.number().min(1).max(10).default(1),
  colorPalette: z.string().optional(),
  aspectRatio: z.enum(['1:1', '16:9', '9:16']).default('1:1'),
  referenceUrls: z.array(z.string()).optional()
});
Corresponding Scenarios

basic_input.json (minimal required fields)

json
{
  "content": "This is sample content for testing the workflow."
}

complete_input.json (all fields specified)

json
{
  "content": "This is sample content for testing the workflow.",
  "numberOfIdeas": 3,
  "colorPalette": "blue and green tones",
  "aspectRatio": "16:9",
  "referenceUrls": [
    "https://example.com/image1.jpg",
    "https://example.com/image2.jpg"
  ]
}

Real-World Example

Based on image_infographic_nano workflow:

test_input_solar_panels.json
json
{
  "content": "Solar panels work by converting sunlight into electricity through the photovoltaic effect. The process begins when photons from sunlight strike the silicon cells in the panel, knocking electrons loose from their atoms. These free electrons flow through the semiconductor material, creating an electric current. The panels contain multiple layers: a protective glass covering, anti-reflective coating to maximize light absorption, silicon cells (both n-type and p-type layers forming a junction), and a backing material. The DC electricity generated by the panels flows through an inverter, which converts it to AC electricity suitable for home use or feeding back into the power grid. Modern solar panels achieve 15-20% efficiency, meaning they convert that percentage of sunlight into usable electricity. The entire system includes mounting hardware, wiring, inverters, and often battery storage for excess energy.",
  "numberOfIdeas": 3,
  "aspectRatio": "16:9",
  "resolution": "2K",
  "numberOfGenerations": 1
}
test_input_complex.json
json
{
  "content": "Detailed explanation of the topic...",
  "numberOfIdeas": 5,
  "colorPalette": "warm earth tones with orange accents",
  "artDirection": "minimalist corporate style",
  "aspectRatio": "1:1",
  "resolution": "4K",
  "numberOfGenerations": 2,
  "referenceImageUrls": [
    "https://storage.example.com/style-guide.png"
  ],
  "storageNamespace": "test/infographics"
}

Running Scenarios

Using CLI
bash
# Run with scenario file
npx output workflow run workflowName --input path/to/scenarios/basic_input.json

# Run with inline JSON
npx output workflow run workflowName --input '{"content": "test"}'
Example Commands
bash
# Basic scenario
npx output workflow run contentUtilsImageInfographicNano --input src/workflows/content_utils/image_infographic_nano/scenarios/test_input_solar_panels.json

# Complex scenario
npx output workflow run contentUtilsImageInfographicNano --input src/workflows/content_utils/image_infographic_nano/scenarios/test_input_complex.json

Related Skill: output-workflow-run for detailed CLI usage

Scenario Categories

1. Basic/Happy Path

Minimal valid input to verify the workflow works:

json
{
  "content": "Simple test content",
  "numberOfIdeas": 1
}

All optional fields populated:

json
{
  "content": "Detailed content...",
  "numberOfIdeas": 5,
  "colorPalette": "custom palette",
  "artDirection": "specific style",
  "aspectRatio": "16:9",
  "resolution": "4K",
  "numberOfGenerations": 3,
  "referenceImageUrls": ["https://example.com/ref.jpg"],
  "storageNamespace": "test/folder"
}
3. Edge Cases

Test boundary conditions:

edge_case_min_values.json

json
{
  "content": "x",
  "numberOfIdeas": 1
}

edge_case_max_values.json

json
{
  "content": "Very long content string...",
  "numberOfIdeas": 10
}
4. Error Cases (for validation testing)

error_missing_required.json

json
{
  "numberOfIdeas": 3
}

Note: Error scenarios won't pass validation but are useful for testing error handling.

Best Practices

Show full SKILL.md (153 more words)Show less
1. Document the Purpose

Add a comment field (if supported) or create a companion README:

json
{
  "_comment": "Tests workflow with multiple reference images",
  "content": "...",
  "referenceImageUrls": ["url1", "url2", "url3"]
}
2. Use Realistic Data
json
{
  "content": "Actual representative content that matches real use cases..."
}

Not:

json
{
  "content": "test"
}
3. Cover All Enum Values

If schema has enums, create scenarios for each:

json
// scenario_aspect_1x1.json
{ "aspectRatio": "1:1", ... }

// scenario_aspect_16x9.json
{ "aspectRatio": "16:9", ... }

// scenario_aspect_9x16.json
{ "aspectRatio": "9:16", ... }
4. Include Optional Field Variations
json
// without_optional_fields.json
{ "content": "..." }

// with_all_optional_fields.json
{ "content": "...", "colorPalette": "...", "artDirection": "..." }

// with_some_optional_fields.json
{ "content": "...", "colorPalette": "..." }
5. Create Regression Test Scenarios

Save inputs from bug reports:

json
// regression_issue_123.json
{
  "_issue": "https://github.com/org/repo/issues/123",
  "content": "Input that caused the bug..."
}

Scenario Organization

For workflows with many scenarios, organize into subfolders:

scenarios/
├── basic/
│   └── minimal_input.json
├── complete/
│   └── all_options.json
├── edge_cases/
│   ├── empty_array.json
│   └── max_length.json
└── regression/
    └── issue_123.json

Verification Checklist

  • Scenario file located in scenarios/ folder inside workflow directory
  • File uses .json extension
  • File name uses snake_case
  • JSON is valid and parseable
  • All required fields from inputSchema are present
  • Field types match schema (strings, numbers, arrays, etc.)
  • Enum values are valid options from schema
  • Numbers are within min/max constraints
  • At least one basic scenario exists
  • Workflow runs successfully with the scenario

Testing Scenarios

Validate JSON Syntax
bash
# Check JSON is valid
cat scenarios/basic_input.json | jq .
Run and Verify
bash
# Run workflow with scenario
npx output workflow run workflowName --input scenarios/basic_input.json

# Check status if async
npx output workflow status <workflowId>

# Get result
npx output workflow result <workflowId>
  • output-dev-types-file - Defining inputSchema that scenarios must match
  • output-dev-folder-structure - Understanding scenarios folder location
  • output-workflow-run - Running workflows with scenario files
  • output-workflow-list - Finding 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-dev-scenario-file of growthxai/output.

Open the folder on GitHubat commit 99ee298

Compare with similar skills

Output Dev Scenario File 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 Dev Scenario File compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Dev Scenario File this skillgrowthxai/output442—~2.1kAutomated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed
  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed
  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed
  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed
  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    381 GitHub starsUsed in 9 repos~2.9k tokens
    Testing & QAAuto-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 Dev Scenario File

What does Output Dev Scenario File do?

Create test scenario JSON files for Output SDK workflows. An agent skill from growthxai/output. Output Dev Scenario File is an agent skill from growthxai/output. Create test scenario JSON files for Output SDK workflows.

When should I use Output Dev Scenario File?

Output Dev Scenario File fits situations like: creating test inputs; documenting expected behaviors; setting up workflow testing.

How do I install Output Dev Scenario File in Claude Code?

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

How do I install Output Dev Scenario File in Codex?

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

Can I use Output Dev Scenario File 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-dev-scenario-file -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-dev-scenario-file, .gemini/skills/output-dev-scenario-file, .github/skills/output-dev-scenario-file and .opencode/skills/output-dev-scenario-file in your project.

What does Output Dev Scenario File need to run?

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

Does Output Dev Scenario File access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Output Dev Scenario File safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Output Dev Scenario File use?

Output Dev Scenario File 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 Dev Scenario File use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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 Dev Scenario File?

Skills that share tags, products or a category with Output Dev Scenario File: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Dev Scenario File?

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.