skills.rest
caelum0x
caelum0xCOMMUNITY
Explore all skills by this author →
GitHub

local-test

Build and run IronClaw web gateway tests locally with Docker and Chrome MCP automation.

Updated Mar 21, 2026
Search Tags:#integration testing#browser automation#mcp#docker#local testing#web gateway
One-click install
npx skills add https://github.com/caelum0x/steelbot --skill local-test-caelum0x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-test
Source: https://github.com/caelum0x/steelbot/tree/main/skills/local-test
Command: npx skills add https://github.com/caelum0x/steelbot --skill local-test-caelum0x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running and verifying IronClaw web gateway changes locally can be slow, error-prone, and environment-dependent, making it hard to confirm that UI, routing, and automation workflows work before deploying.

Core Features & Use Cases

  • Docker-based local test environment: Build and run a dedicated Docker image (using Dockerfile.test) so you can validate the web gateway behavior without needing your full production stack.
  • Configurable LLM backends: Start the container with NEAR AI, OpenAI, Anthropic, or a dummy mode to focus on UI loading and gateway wiring.
  • Chrome MCP browser automation workflow: Use MCP tools to open the local gateway, verify the page, capture screenshots, and test interactions (including mobile viewport checks).

Quick Start

Build the test image with Dockerfile.test, then run the container on port 3003 with ONBOARD_COMPLETED=true and CLI_ENABLED=false, and open http://localhost:3003/?token=test in your browser.

Frequently Asked Questions about local-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test web gateway changes locally using Docker and browser automation?▼

Test web gateway changes locally by building a dedicated Docker image from Dockerfile.test, running the container with the correct environment variables, and executing a deterministic MCP step sequence to open, inspect, and verify the page.

Can I validate interactive web pages across different viewports with Chrome MCP?▼

Yes, Chrome MCP browser automation validates interactive web pages by opening the local gateway, verifying UI connectivity, capturing screenshots, and smoke-testing interactions across both desktop and mobile viewports.

What environment variables are required to run local testing for web gateway behavior?▼

Local testing for web gateway behavior requires setting gateway environment variables like ONBOARD_COMPLETED=true and CLI_ENABLED=false, along with configurable LLM backend settings for NEAR AI, OpenAI, Anthropic, or dummy mode.

How does Docker-based local testing help verify UI and routing before deployment?▼

Docker-based local testing builds a dedicated test image to validate UI loading, routing, and gateway wiring without needing the full production stack, ensuring automation workflows function correctly before deployment.

Do I need a full production stack to smoke-test gateway and auth behavior locally?▼

No, you do not need a full production stack to smoke-test gateway and auth behavior locally; building and running a Dockerfile.test-based image isolates the environment to focus on UI connectivity and gateway behavior.

Related Skills

Explore More Software Engineering Skills→
nearainearai
12.6k

local-test

Build and run a Dockerized IronClaw web gateway test environment with Chrome MCP browser automation.

Official
Intermediate
onbluerosesonblueroses
3

mobile-preview

Capture mobile viewport screenshots of web pages to test responsiveness.

Community
Basic
chtughachtugha

local-test

Automate local testing of BrassClaw's web gateway with Docker and Chrome MCP.

Community
Intermediate
wdappwdapp

local-test

Automate Docker container creation for local IronClaw web gateway testing.

Community
Intermediate