web-ui-test

Verify IronClaw web gateway UI and Skills workflow through manual browser testing.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/caelum0x/steelbot --skill web-ui-test-caelum0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-ui-test
Source: https://github.com/caelum0x/steelbot/tree/main/skills/web-ui-test
Command: npx skills add https://github.com/caelum0x/steelbot --skill web-ui-test-caelum0x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly confirm that the IronClaw web gateway UI is functioning correctly after setup or changes, reducing uncertainty during manual QA.

Core Features & Use Cases

  • Gateway UI smoke testing: Validate that the web gateway is reachable and that the connection/auth indicator reflects the expected state.
  • Chat, Skills, and navigation checks: Ensure core UI sections load (Chat, Memory, Jobs, Routines, Extensions, Skills) and that Skills search and install/remove flows work.
  • Extension-like browser testing guidance: Use Claude for Chrome to test the web UI with the expected user journey and capture common failure signals (e.g., registry unreachable or missing UI system errors).

Quick Start

Run IronClaw with GATEWAY_ENABLED enabled using CLI_ENABLED=false and GATEWAY_AUTH_TOKEN set, then open the gateway URL in your browser with the token parameter to verify the UI loads and the Skills tab works.

Frequently Asked Questions about web-ui-test

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

FAQPage Schema
How do I manually test a web gateway UI for connection status and navigation?

To manually test a web gateway UI, verify the connection and auth indicators, navigate through core sections like Chat and Memory, and confirm that search and install flows function correctly in the browser.

What do I need to verify Skills search and installation in a web gateway?

Verifying Skills search and installation requires enabling the gateway, setting a valid authentication token, and ensuring a reachable ClawHub registry endpoint to confirm UI search and install behaviors.

How do I check if a registry endpoint is unreachable during browser-based QA testing?

You can check for an unreachable registry endpoint during browser-based QA by navigating to the Skills tab and looking for missing UI system errors or failed search and install behaviors.

Can I use a browser extension to test web UI navigation tabs and user journeys?

Yes, you can use a browser extension like Claude for Chrome to test the web UI navigation tabs, execute the expected user journey, and capture common failure signals during manual QA.

Why is my web gateway UI not loading after setup changes?

Your web gateway UI may not load if the gateway is not enabled, the authentication token is missing or invalid, or the ClawHub registry endpoint is unreachable during your manual QA check.