Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Create test scenario JSON files for Output SDK workflows. An agent skill from growthxai/output.
$ npx skills add growthxai/output --skill output-dev-scenario-file -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install growthxai/output output-dev-scenario-file --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "output-dev-scenario-file" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file into .claude/skills/output-dev-scenario-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-scenario-file", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-fileType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add growthxai/output --skill output-dev-scenario-file -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install growthxai/output output-dev-scenario-file --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file .agents/skills/output-dev-scenario-file && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "output-dev-scenario-file" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file into .agents/skills/output-dev-scenario-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-scenario-file", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add growthxai/output --skill output-dev-scenario-file -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install growthxai/output output-dev-scenario-file --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file .cursor/skills/output-dev-scenario-file && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "output-dev-scenario-file" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file into .cursor/skills/output-dev-scenario-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-scenario-file", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/growthxai/output.git --path coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add growthxai/output --skill output-dev-scenario-file -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install growthxai/output output-dev-scenario-file --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file .gemini/skills/output-dev-scenario-file && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "output-dev-scenario-file" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file into .gemini/skills/output-dev-scenario-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-scenario-file", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install growthxai/output output-dev-scenario-fileInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add growthxai/output --skill output-dev-scenario-file -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .github/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file .github/skills/output-dev-scenario-file && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "output-dev-scenario-file" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file into .github/skills/output-dev-scenario-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-scenario-file", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add growthxai/output --skill output-dev-scenario-file -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install growthxai/output output-dev-scenario-file --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file .opencode/skills/output-dev-scenario-file && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "output-dev-scenario-file" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file into .opencode/skills/output-dev-scenario-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-scenario-file", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
output-dev-scenario-fileCreate 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. 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.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 99ee298. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxjqFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from growthxai/output at commit 99ee298, republished under its Apache-2.0 licence (© growthxai). 376 words, ~2,128 tokens.
.claude/skills/output-dev-scenario-file/SKILL.md (or your agent's skills folder).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.
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.jsonImportant: Scenarios are workflow-specific and live inside the workflow folder.
Use snake_case for scenario file names:
{description}_input.jsonExamples:
basic_input.jsontest_input_solar_panels.jsonedge_case_empty_content.jsoncomplex_with_references.jsonNaming patterns:
basic_* - Minimal valid inputcomplex_* - Full-featured input with all optionsedge_case_* - Boundary conditions and edge caseserror_* - Inputs expected to produce errorsA scenario file is a JSON file that matches the workflow's inputSchema:
{
"fieldName": "value",
"optionalField": "optional value",
"numericField": 42,
"arrayField": ["item1", "item2"]
}The scenario JSON must match the Zod schema defined in types.ts:
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()
});basic_input.json (minimal required fields)
{
"content": "This is sample content for testing the workflow."
}complete_input.json (all fields specified)
{
"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"
]
}Based on image_infographic_nano workflow:
{
"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
}{
"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"
}# 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"}'# 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.jsonRelated Skill: output-workflow-run for detailed CLI usage
Minimal valid input to verify the workflow works:
{
"content": "Simple test content",
"numberOfIdeas": 1
}All optional fields populated:
{
"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"
}Test boundary conditions:
edge_case_min_values.json
{
"content": "x",
"numberOfIdeas": 1
}edge_case_max_values.json
{
"content": "Very long content string...",
"numberOfIdeas": 10
}error_missing_required.json
{
"numberOfIdeas": 3
}Note: Error scenarios won't pass validation but are useful for testing error handling.
Add a comment field (if supported) or create a companion README:
{
"_comment": "Tests workflow with multiple reference images",
"content": "...",
"referenceImageUrls": ["url1", "url2", "url3"]
}{
"content": "Actual representative content that matches real use cases..."
}Not:
{
"content": "test"
}If schema has enums, create scenarios for each:
// scenario_aspect_1x1.json
{ "aspectRatio": "1:1", ... }
// scenario_aspect_16x9.json
{ "aspectRatio": "16:9", ... }
// scenario_aspect_9x16.json
{ "aspectRatio": "9:16", ... }// without_optional_fields.json
{ "content": "..." }
// with_all_optional_fields.json
{ "content": "...", "colorPalette": "...", "artDirection": "..." }
// with_some_optional_fields.json
{ "content": "...", "colorPalette": "..." }Save inputs from bug reports:
// regression_issue_123.json
{
"_issue": "https://github.com/org/repo/issues/123",
"content": "Input that caused the bug..."
}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.jsonscenarios/ folder inside workflow directory.json extensionsnake_case# Check JSON is valid
cat scenarios/basic_input.json | jq .# 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 matchoutput-dev-folder-structure - Understanding scenarios folder locationoutput-workflow-run - Running workflows with scenario filesoutput-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
Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-dev-scenario-file of growthxai/output.
Open the folder on GitHubat commit 99ee298
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Output Dev Scenario File this skillgrowthxai/output | 442 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 32 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
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…
growthxai/output
Implement an Output SDK workflow from a plan document. An agent skill from growthxai/output.
growthxai/output
View, edit, and set encrypted credentials in an Output.ai project.
growthxai/output
Wire encrypted credentials to environment variables using the credential: convention.
growthxai/output
Initialize encrypted credentials for an Output.ai project. An agent skill from growthxai/output.
growthxai/output
Debug Output SDK workflow issues. An agent skill from growthxai/output.
growthxai/output
Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.
Categories
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.
Output Dev Scenario File fits situations like: creating test inputs; documenting expected behaviors; setting up workflow testing.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.