hub-pro-mac-session

Enforces lightweight session rules preventing validator stalls during Mac founder work.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During founder sessions on Mac, agents can get stuck running heavy end-to-end validators for 11+ minutes, blocking responses and harming productivity. This Skill enforces strict session rules so agents reply fast, run only light checks, and defer heavy validation to cloud CI. ## Core Features & Use Cases - Validator Stall Prevention: Bans validator marathons, chained validate commands, and heavy build gates during founder sessions, with a hard 90-second limit on shell commands. - Receipt-Based Proof: Uses pre-generated receipt JSON files in ~/.sina/ as proof of state instead of re-running validation loops. - Light Health Checks: Permits quick curl health checks and single light script runs to confirm system state. - Use Case: A founder asks an agent on Mac whether the hub is healthy. Instead of running a full e2e suite, the agent curls the local health endpoint and reads the latest receipt file, answering in under 30 seconds. ## Quick Start Apply the hub-pro-mac-session rules and answer my question using only light checks and receipt files, without running any heavy validators.

Frequently Asked Questions about hub-pro-mac-session

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

FAQPage Schema
How do I avoid getting stuck in validators during a Mac founder session?

Run at most one light shell command under 90 seconds per turn and never chain validate commands. Use receipt JSON files in ~/.sina/ as proof of state instead of re-running validation loops.

What checks are allowed during a Hub Pro Mac founder session?

Allowed checks include curling the local health endpoint at 127.0.0.1:13020, running the hub_pro_skills_v1.py script with JSON output, and reading receipt files like hub-form-submit-receipt-v1.json.

Where does heavy e2e validation run if not on Mac?

Heavy validation runs on Railway or cloud CI during the ship window. Touch the asf-ship-window-v1.flag file to gate build scripts that check for the founder session flag.

Why is chaining validate commands forbidden on Mac?

Chained validators can run for 11+ minutes, which blocks founder responses and is classified as a P0 incident. Proof should come from existing receipts, not validator marathons.

Can the Mac control plane call cloud APIs?

Yes, the api-disabled-v1.flag must be absent so Mac can call cloud APIs. Mac acts as a control panel only, with local CLI drain disabled via the cli-disabled-v1.flag.