菜单
Enforce one-brain routing across VRM Sandbox, PC Control, and MemryX shim with shim-first public endpoint authority on port 9000. Use when VRM chat/control behavior must be governed by PC Control without changing the public model-plane endpoint.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | shim-pc-control-brain-routing |
| description | Enforce one-brain routing across VRM Sandbox, PC Control, and MemryX shim with shim-first public endpoint authority on port 9000. Use when VRM chat/control behavior must be governed by PC Control without changing the public model-plane endpoint. |
Use this skill when the operator wants:
http://127.0.0.1:90009000.G:\GitHub; treat legacy Documents\GitHub paths only as aliases to report and correct.http://127.0.0.1:2337/v1 as authoritative alongside the shim public plane.http://127.0.0.1:1234/v1 only as a non-authoritative operator surface when it is present.127.0.0.1:9000127.0.0.1:2337127.0.0.1:1234127.0.0.1:8890127.0.0.1:5175GET /v1/agent-fabric/contracts/endpointsGET /v1/agent-fabric/models/localPOST /v1/agent-fabric/local-agent/chat (research-only prompt)Invoke-RestMethod http://127.0.0.1:9000/v1/models?health=1
Invoke-RestMethod http://127.0.0.1:2337/v1/models
Invoke-RestMethod http://127.0.0.1:9000/api/agent/auth-status
Invoke-RestMethod http://127.0.0.1:8890/v1/agent-fabric/contracts/endpoints
Invoke-RestMethod http://127.0.0.1:8890/v1/agent-fabric/models/local
Invoke-RestMethod http://127.0.0.1:5175/runtime/health
9000) unless operator explicitly overrides.:1234 or other legacy direct ports become the authority source in docs, scripts, or validation examples.Use this skill for cross-repo routing alignment among:
If the request expands beyond these lanes, route through $skill-hub.
references/routing-contract.mdIf evidence is incomplete or contradictory:
9000 public-lane contract is re-confirmedRun the local NullClaw host security app for skill governance, curated-source discovery, guarded threat suppression, and self-governance on Windows hosts.
Sweep one or more local repositories for implementation gaps and produce deterministic, evidence-backed remediation lanes. Use when you need cross-repo detection of missing tests, docs lockstep drift, risky TODO/FIXME additions, and release-hygiene misses.
Build and query bounded metadata-only repository indexes without rg process churn. Use when working in very large repos and you need deterministic file discovery by path, extension, language, scope, or freshness.
Detect recent cross-repo work and produce deterministic JSON evidence for skill curation and routing decisions. Use when workflows span multiple repos and you need a bounded view of recent commits, touched files, and policy/contract-sensitive changes.
Enforce hardware-first diagnosis and fixes in <PRIVATE_REPO_B>. Use for runtime probe, telemetry, inference, and integration failures where strict real-hardware behavior, no new stubs, deterministic diagnostics, and no unrequested driver/runtime mutation are required.
Run a defender-first security sweep on code, configs, prompts, model/tooling surfaces, or third-party contribution lanes. Use when a request involves safe bug, leak, zero-day-class, exploit, or hack hunting for protection, when contributing to outside repositories and you want a focused security pass, or when touching auth, secrets, permissions, network exposure, prompt/tool boundaries, data flow, or update/build surfaces. This skill is defensive only and must never be used for weaponization or unauthorized access.