skills.rest
different-ai
different-aiOFFICIAL
Explore all skills by this author →
𝕏@benjaminshafiiGitHub

openwork-testability

Coordinate headless UI testing for OpenWork messaging and session flows.

63|8|Updated Jan 24, 2026
Search Tags:#automation#qa#testability#ui-testing#headless#openwork
One-click install
npx skills add https://github.com/different-ai/openwork-enterprise --skill openwork-testability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openwork-testability
Source: https://github.com/different-ai/openwork-enterprise/tree/main/.opencode/skills/openwork-testability
Command: npx skills add https://github.com/different-ai/openwork-enterprise --skill openwork-testability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Make testing sending a message via the UI a core part of OpenWork testability. Use dev:web + headless as the default testing pairing.

Core Features & Use Cases

  • Start headless in an empty workspace with a non-default port to enable parallel runs.
  • Start the web UI on a non-default port and connect the UI to headless to exercise the OpenWork UI flow.
  • Create a session, send a short message, and capture logs for validation across both headless and UI components.

Quick Start

Start the headless in an empty workspace, then start the web UI, connect them, and run a test session to verify messaging through the UI.

Frequently Asked Questions about openwork-testability

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

FAQPage Schema
How do I automate UI testing for messaging and session flows?▼

Automate UI testing for messaging and session flows by coordinating a headless backend with a web UI. This process connects both components, exchanges messages across specified ports, and captures logs to validate the session interactions.

Can I run headless UI tests and web UI sessions on non-default ports?▼

Yes, you can run headless UI tests and web UI sessions on non-default ports. Starting headless in an empty workspace with explicit port choices enables parallel runs and enforces deterministic execution across both components.

What is the best way to verify a UI message send flow in OpenWork?▼

The best way to verify a UI message send flow in OpenWork is using the dev:web and headless pairing. Start headless, start the web UI, connect them, create a session, send a short message, and capture logs for validation.

How do I capture logs from both headless and web UI sessions?▼

Capture logs from both headless and web UI sessions by running a coordinated test session. Once the web UI connects to the headless backend, send a short message through the interface to log the results from both components.

Why does deterministic execution matter for headless UI testing?▼

Deterministic execution matters for headless UI testing because it ensures reliable, repeatable test results. Explicit port choices prevent conflicts during parallel runs, keeping the messaging and session flow validations stable across components.

Related Skills

Explore More Software Engineering Skills→
tech-with-sethtech-with-seth
4

playwright-cli

Automate browser UI tests using Playwright CLI commands.

Official
Advanced
tutur3ututur3u
53

agent-browser

Drive the agent-browser CLI to navigate pages, fill forms, and extract data.

Official
Advanced
shariqazeemshariqazeem
1

controller-backend

Integrate Cartridge Controller into Node.js, Rust, and C++ backends for programmatic Starknet transactions.

Community
Advanced
brsblbrsbl
14

browser

Automate browser tasks to inspect UI, capture screenshots, fill forms, and extract page data.

Community
Intermediate