How do I install the Repo B Local Bridge Orchestrator skill?

Run npx skillmds@latest add tomevault-io/repo-b-local-bridge-orchestrator 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 Local Bridge Orchestrator 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 Local Bridge Orchestrator?

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 Local Bridge Orchestrator free to use?

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

Who published Repo B Local Bridge Orchestrator?

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

Repo B Local Bridge Orchestrator by tomevault-io

Name: Repo B Local Bridge Orchestrator
Author: tomevault-io

Repo B Local Bridge Orchestrator

Run credit-first local Agent Bridge orchestration in <PRIVATE_REPO_B> with strict read-only validation, bounded indexing, and fail-closed guidance hints. Excludes MCP Comfy diagnostics. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

REPO_B Local Bridge Orchestrator

Use this skill to run a manual local-first Agent Bridge workflow in <PRIVATE_REPO_B> and emit validated guidance hints without cloud fallback.

Scope Boundary

In scope: /api/agent/* readiness/tasks, bounded file indexing, analyze_files validation, and guidance hint output.
Out of scope: /api/mcp/* operations and shim.comfy.* diagnostics.
For MCP/Comfy operations, use $repo-b-mcp-comfy-bridge.

Workflow

Confirm policy-safe environment (read_only, fail-closed).
Probe bridge readiness (/health, /api/agent/capabilities).
Build or refresh bounded metadata index on demand.
Query candidate files for the selected scope.
Submit read-only analyze_files task (allow_write=false, dry_run=true).
Validate bridge response with strict schema/evidence/confidence gates.
Emit normalized guidance_hints JSON and stop on failures.

Drop-In Hook Files

Copy these files into <PRIVATE_REPO_B> before first run:

assets/repo_b/tools/local_bridge_orchestrator.py -> tools/local_bridge_orchestrator.py
assets/repo_b/tools/local_bridge_validate.py -> tools/local_bridge_validate.py
assets/repo_b/tools/local_bridge_orchestrator.example.env -> tools/local_bridge_orchestrator.example.env
assets/repo_b/tests/tools/test_local_bridge_orchestrator.py -> tests/tools/test_local_bridge_orchestrator.py
assets/repo_b/tests/tools/test_local_bridge_validate.py -> tests/tools/test_local_bridge_validate.py

Required Environment (PowerShell)

$env:REPO_B_LOCAL_ORCH_ENABLED = "1"
$env:REPO_B_LOCAL_ORCH_CONFIDENCE_MIN = "0.85"
$env:REPO_B_LOCAL_ORCH_EVIDENCE_MIN = "2"
$env:REPO_B_LOCAL_ORCH_FAIL_CLOSED = "1"
$env:REPO_B_LOCAL_ORCH_MAX_HINTS = "12"
$env:REPO_B_CONTINUE_BRIDGE_ENABLED = "1"
$env:REPO_B_CONTINUE_MODE = "read_only"
$env:REPO_B_CONTINUE_ALLOWED_ROOTS = "G:\GitHub\<PRIVATE_REPO_B>"

Run Command

Run from <PRIVATE_REPO_B> root:

python tools/local_bridge_orchestrator.py \
  --task ticket-123 \
  --prompt-file .codex/local_prompts/ticket-123.txt \
  --scope connector \
  --json-out .codex/local_bridge/ticket-123.json

Usage Guardrails

Use your real usage history before scale-up:

python3 "$CODEX_HOME/skills/usage-watcher/scripts/usage_guard.py" analyze \
  --input /path/to/usage.csv \
  --window-days 30 \
  --format table

python3 "$CODEX_HOME/skills/usage-watcher/scripts/usage_guard.py" plan \
  --monthly-budget <credits> \
  --reserve-percent 20 \
  --work-days-per-week 5 \
  --sessions-per-day 3 \
  --burst-multiplier 1.5 \
  --format table

Authority reminder:

Treat http://127.0.0.1:9000/v1 and http://127.0.0.1:2337/v1 as authoritative model lanes.
Treat http://127.0.0.1:1234/v1 only as a non-authoritative operator surface.

References

references/orchestrator-workflow.md
references/validation-contract.md
references/mx3-phase2-roadmap.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-local-bridge-orchestratordescription: Run credit-first local Agent Bridge orchestration in <PRIVATE_REPO_B> with strict read-only validation, bounded indexing, and fail-closed guidance hints. Excludes MCP Comfy diagnostics. Use when this capability is needed.---# REPO_B Local Bridge OrchestratorUse this skill to run a manual local-first Agent Bridge workflow in `<PRIVATE_REPO_B>` and emit validated guidance hints without cloud fallback.## Scope Boundary- In scope: `/api/agent/*` readiness/tasks, bounded file indexing, `analyze_files` validation, and guidance hint output.- Out of scope: `/api/mcp/*` operations and `shim.comfy.*` diagnostics.- For MCP/Comfy operations, use `$repo-b-mcp-comfy-bridge`.## Workflow1. Confirm policy-safe environment (`read_only`, fail-closed).2. Probe bridge readiness (`/health`, `/api/agent/capabilities`).3. Build or refresh bounded metadata index on demand.4. Query candidate files for the selected scope.5. Submit read-only `analyze_files` task (`allow_write=false`, `dry_run=true`).6. Validate bridge response with strict schema/evidence/confidence gates.7. Emit normalized `guidance_hints` JSON and stop on failures.## Drop-In Hook FilesCopy these files into `<PRIVATE_REPO_B>` before first run:- `assets/repo_b/tools/local_bridge_orchestrator.py` -> `tools/local_bridge_orchestrator.py`- `assets/repo_b/tools/local_bridge_validate.py` -> `tools/local_bridge_validate.py`- `assets/repo_b/tools/local_bridge_orchestrator.example.env` -> `tools/local_bridge_orchestrator.example.env`- `assets/repo_b/tests/tools/test_local_bridge_orchestrator.py` -> `tests/tools/test_local_bridge_orchestrator.py`- `assets/repo_b/tests/tools/test_local_bridge_validate.py` -> `tests/tools/test_local_bridge_validate.py`## Required Environment (PowerShell)```powershell$env:REPO_B_LOCAL_ORCH_ENABLED = "1"$env:REPO_B_LOCAL_ORCH_CONFIDENCE_MIN = "0.85"$env:REPO_B_LOCAL_ORCH_EVIDENCE_MIN = "2"$env:REPO_B_LOCAL_ORCH_FAIL_CLOSED = "1"$env:REPO_B_LOCAL_ORCH_MAX_HINTS = "12"$env:REPO_B_CONTINUE_BRIDGE_ENABLED = "1"$env:REPO_B_CONTINUE_MODE = "read_only"$env:REPO_B_CONTINUE_ALLOWED_ROOTS = "G:\GitHub\<PRIVATE_REPO_B>"```## Run CommandRun from `<PRIVATE_REPO_B>` root:```bashpython tools/local_bridge_orchestrator.py \ --task ticket-123 \ --prompt-file .codex/local_prompts/ticket-123.txt \ --scope connector \ --json-out .codex/local_bridge/ticket-123.json```## Usage GuardrailsUse your real usage history before scale-up:```bashpython3 "$CODEX_HOME/skills/usage-watcher/scripts/usage_guard.py" analyze \ --input /path/to/usage.csv \ --window-days 30 \ --format table``````bashpython3 "$CODEX_HOME/skills/usage-watcher/scripts/usage_guard.py" plan \ --monthly-budget <credits> \ --reserve-percent 20 \ --work-days-per-week 5 \ --sessions-per-day 3 \ --burst-multiplier 1.5 \ --format table```Authority reminder:- Treat `http://127.0.0.1:9000/v1` and `http://127.0.0.1:2337/v1` as authoritative model lanes.- Treat `http://127.0.0.1:1234/v1` only as a non-authoritative operator surface.## References- `references/orchestrator-workflow.md`- `references/validation-contract.md`- `references/mx3-phase2-roadmap.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