How do I install the Repo B Control Center Ops skill?

Run npx skillmds@latest add tomevault-io/repo-b-control-center-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo B Control Center Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo B Control Center Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo B Control Center Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo B Control Center Ops?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo B Control Center Ops by tomevault-io

Name: Repo B Control Center Ops
Author: tomevault-io

Repo B Control Center Ops

Operate and debug <PRIVATE_REPO_B> Control Center and thin-waist service surfaces. Use when working on connector routing, Lighthouse checks, MCP/Agent Bridge endpoints, pose bridge, canonical desktop startup/restart behavior, shortcut ownership, or window lifecycle/state ownership. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

REPO_B Shim Control Center Ops

Use this skill for Control Center runtime and service-surface operations.

Workflow

Start or restart using the canonical repo-owned desktop path.
Close stale repo-owned windows/processes before relaunch.
Validate API readiness and endpoint contracts.
Debug connector routing, diagnostics windows, and startup state restore.
Validate desktop/window lifecycle ownership and verify no duplicate bounds/maximize/fullscreen ownership outside the window manager.
Enforce startup acceptance:
- no visible empty console windows
- no stale-window relaunches
- frontend plus backend together
- shortcuts/icons target the latest repo-owned launcher
Capture endpoint, window-manager, and launcher evidence for each restart fix.

Scope Boundary

Use this skill for Control Center startup/restart behavior and service-surface readiness checks.

Do not use this skill for:

Windows-host vs WSL split diagnostics lane.
Strict real-hardware probe/root-cause lane.
PR preflight and docs lockstep gate lane.

Canonical Operations

powershell -ExecutionPolicy Bypass -File .\scripts\Start-ControlCenter.ps1
powershell -ExecutionPolicy Bypass -File .\scripts\stop.ps1

curl http://127.0.0.1:9000/health
curl http://127.0.0.1:9000/v1/models
curl http://127.0.0.1:9000/api/resources
curl http://127.0.0.1:9000/api/mcp/status
curl http://127.0.0.1:9000/api/agent/capabilities

Desktop Window and Layout Checks

From <PRIVATE_REPO_B> root:

python -m pytest apps/mx3-control-center/tests

cd apps/mx3-control-center/web/electron
npm test -- windowBounds.test.js windowManager.test.js

From <PRIVATE_REPO_B>/apps/mx3-control-center/web:

npm run build

Contract Guardrails

Keep documented Control Center and startup diagnostics endpoints stable unless migration is approved.
Keep connector routing and endpoint behavior backward-compatible.
Preserve existing boundary for desktop window lifecycle: one authoritative window manager module, no duplicate bounds state ownership.
Keep hidden/windowless launch limited to secondary helper processes, not the canonical desktop startup path.
Treat Electron/embedded-Node ABI ownership and ORT provider readiness as part of the shipped startup contract when those lanes change.

References

Endpoint checklist: references/control-center-endpoints.md

Loopback

If this lane is unresolved, blocked, or ambiguous:

Capture current evidence and failure context.
Route back through $skill-hub for chain recalculation.
Resume only after the updated chain returns a deterministic next step.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: repo-b-control-center-opsdescription: Operate and debug <PRIVATE_REPO_B> Control Center and thin-waist service surfaces. Use when working on connector routing, Lighthouse checks, MCP/Agent Bridge endpoints, pose bridge, canonical desktop startup/restart behavior, shortcut ownership, or window lifecycle/state ownership. Use when this capability is needed.---# REPO_B Shim Control Center OpsUse this skill for Control Center runtime and service-surface operations.## Workflow1. Start or restart using the canonical repo-owned desktop path.2. Close stale repo-owned windows/processes before relaunch.3. Validate API readiness and endpoint contracts.4. Debug connector routing, diagnostics windows, and startup state restore.5. Validate desktop/window lifecycle ownership and verify no duplicate bounds/maximize/fullscreen ownership outside the window manager.6. Enforce startup acceptance: - no visible empty console windows - no stale-window relaunches - frontend plus backend together - shortcuts/icons target the latest repo-owned launcher7. Capture endpoint, window-manager, and launcher evidence for each restart fix.## Scope BoundaryUse this skill for Control Center startup/restart behavior and service-surface readiness checks.Do not use this skill for:1. Windows-host vs WSL split diagnostics lane.2. Strict real-hardware probe/root-cause lane.3. PR preflight and docs lockstep gate lane.## Canonical Operations```powershellpowershell -ExecutionPolicy Bypass -File .\scripts\Start-ControlCenter.ps1powershell -ExecutionPolicy Bypass -File .\scripts\stop.ps1``````bashcurl http://127.0.0.1:9000/healthcurl http://127.0.0.1:9000/v1/modelscurl http://127.0.0.1:9000/api/resourcescurl http://127.0.0.1:9000/api/mcp/statuscurl http://127.0.0.1:9000/api/agent/capabilities```## Desktop Window and Layout ChecksFrom `<PRIVATE_REPO_B>` root:```bashpython -m pytest apps/mx3-control-center/tests``````bashcd apps/mx3-control-center/web/electronnpm test -- windowBounds.test.js windowManager.test.js```From `<PRIVATE_REPO_B>/apps/mx3-control-center/web`:```bashnpm run build```## Contract Guardrails- Keep documented Control Center and startup diagnostics endpoints stable unless migration is approved.- Keep connector routing and endpoint behavior backward-compatible.- Preserve existing boundary for desktop window lifecycle: one authoritative window manager module, no duplicate bounds state ownership.- Keep hidden/windowless launch limited to secondary helper processes, not the canonical desktop startup path.- Treat Electron/embedded-Node ABI ownership and ORT provider readiness as part of the shipped startup contract when those lanes change.## References- Endpoint checklist: `references/control-center-endpoints.md`## LoopbackIf this lane is unresolved, blocked, or ambiguous:1. Capture current evidence and failure context.2. Route back through `$skill-hub` for chain recalculation.3. Resume only after the updated chain returns a deterministic next step.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/grtninja) — claim your Tome and manage your conversions.

Frequently asked questions