hub-pro-hub-hero

Diagnoses and operates Hub services, Cloud Workers, API Station, and Mac Health Guard endpoints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It resolves the recurring confusion between LIVE server pipes and OFFLINE UI surfaces when operating the Hub portfolio apps, giving agents a single field playbook for health checks, restarts, and founder-session operations. ## Core Features & Use Cases - Port and health map: Documents health endpoints for Worker Hub H1, Machine Hub H2, Official Form, Mac Health Guard, Chat Unify, and n8n Integration so agents can verify services with curl. - Cloud Workers command center: Covers the cloud-workers API, the Hub-only proceed route, receipt files, and how to distinguish motor failures from pipe outages. - API Station and form operations: Explains the shared api-station-tab.js, the 44+ ops catalog requirement, and founder-only form submission rules including INCIDENT-037. - Use Case: An agent sees the Machine Hub page showing OFFLINE while the server responds; the playbook directs splitting server health from JS/DOM errors, null-guarding DOM ids, and proving the fix with receipts. ## Quick Start Ask the agent to check Hub health for worker_hub and read the Hub Pro checklist before shipping a bounded UI fix.

Frequently Asked Questions about hub-pro-hub-hero

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

FAQPage Schema
How do I check Hub app health from the command line?

Run curl against each documented health endpoint, such as curl -sf http://127.0.0.1:13020/health for Worker Hub or port 13024 for Mac Health Guard. The playbook maps every app to its port and health route.

Why does the Hub page show OFFLINE when the server is running?

The pipe can be LIVE while the UI shows OFFLINE because of JS or DOM errors, such as removed element ids without null guards in app.js. Split server health from surface errors, fix the DOM issue, then prove it with receipts.

How do I restart the Hub after editing shared JS files?

Run launchctl kickstart -k gui/$(id -u)/com.sourcea.hub after editing sina-command-server.py or shared tab scripts. Hard refresh the browser or WKWebView afterward so cached api-station-tab.js or hub-pro-skills-tab.js is replaced.

Why does Cloud Workers proceed fail while the Hub pipe is live?

Proceed failures usually come from a stale Railway image or failed motor, not a missing Hub route. Read the classification in the receipt: pipe_live, stale_image, or motor_failed, and only use the Hub proceed endpoint, not the Mac FORGE motor.

Can agents submit rows through the Official Form?

No. Per INCIDENT-037 the Official Form is founder-only; agents must not submit form rows. The button must read SUBMIT and partial batches with one or more explicit picks are acceptable for the founder.