hub-pro-app-e2e

Runs health probes, port checks, and smoke tests across Hub Pro app services.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-app-e2e-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hub-pro-app-e2e
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/hub-pro-app-e2e
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-app-e2e-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that every Hub Pro app service is alive and correctly wired requires manually probing multiple ports, APIs, and UI links, which is error-prone and easy to skip. This Skill provides a single reference for the port map, health endpoints, e2e sequences, and known failure fixes. ## Core Features & Use Cases - Port and health matrix: Documents each service (Cloud Workers on 13027, Chat Unify on 13023, Mac Health on 13024, n8n on 13026, Mac Law on 8781) with its health endpoint and primary API. - Founder-safe smoke tests: Provides curl-based e2e sequences and a verify-founder-desktop-apps script that boots apps if they are down. - Troubleshooting playbook: Lists observed failure symptoms (load failures, empty form replies, offline status, dead links) with their causes and fixes. - Use Case: After restarting a Mac, run the documented curl probes against 127.0.0.1 ports to confirm Cloud Workers, Chat Unify, and Mac Health are live before starting founder operations. ## Quick Start Ask the assistant to run the Hub Pro e2e health checks across all app ports and report which services are live or down.

Frequently Asked Questions about hub-pro-app-e2e

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

FAQPage Schema
How do I run health checks on local app services?

Run curl -sf against each service's health endpoint, such as http://127.0.0.1:13027/health for Cloud Workers and http://127.0.0.1:13023/health for Chat Unify. A non-zero exit code indicates the service is down.

How do I smoke test multiple local web apps after a reboot?

Probe each app's health endpoint in sequence with curl, then run the verify-founder-desktop-apps-v1.sh script which boots apps that are down. Confirm results via receipt files rather than UI status messages.

Why does a local app show offline even though the server is running?

A common cause is JavaScript null errors on removed DOM elements, as seen with Mac Health showing OFFLINE due to a missing grid element. Adding null guards in the frontend code resolves the false offline status.

Should I use localhost or 127.0.0.1 for cross-app URLs?

Use 127.0.0.1 for cross-app URLs to avoid localhost resolution drift between services. The link wire checklist explicitly requires 127.0.0.1 for consistent routing across Hub apps.

What are the limitations of curl-based health probes?

Curl health probes only confirm an HTTP endpoint responds; they do not validate deeper business logic or form submission flows. For full verification, combine probes with receipt files that prove operations actually completed.