Assists with refactoring relay and control-plane logic in standalone remote systems.
Install
mkdir -p .claude/skills/bridge-handler-task && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15457" && unzip -o skill.zip -d .claude/skills/bridge-handler-task && rm skill.zipInstalls to .claude/skills/bridge-handler-task
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when adding or refactoring relay/control-plane behavior, bridge-managed RPCs, or desktop-agent forwarding behavior in the standalone remote stack.Key capabilities
- →Implement backend/runtime changes.
- →Refactor relay/control-plane behavior.
- →Refactor bridge-managed RPCs.
- →Refactor desktop-agent forwarding behavior.
- →Preserve `/api/mobile/*` and `/v1/sessions/*` compatibility.
How it works
The skill guides changes in the standalone remote stack by reading `.codex/rules/bridge-and-relay.md`, confirming the change's location (control-plane, bridge, or desktop relay agent), and preserving existing API compatibility. It normalizes structured errors and keeps desktop-side assumptions clear.
Inputs & outputs
When to use bridge-handler-task
- →Refactor relay agent forwarding
- →Update bridge-managed RPC logic
- →Implement new control-plane behavior
About this skill
Bridge Handler Task
Use this skill when adding or refactoring relay/control-plane behavior, bridge-managed RPCs, or desktop-agent forwarding behavior in the standalone remote stack.
Goal
Implement backend/runtime changes without destabilizing the browser contract or the bridge session lifecycle.
Workflow
- Read
.codex/rules/bridge-and-relay.md. - Confirm whether the change belongs in the control-plane, bridge, or desktop relay agent.
- Preserve
/api/mobile/*and/v1/sessions/*compatibility unless the task explicitly changes them. - Normalize structured errors instead of leaking raw process failures where possible.
- Keep desktop-side assumptions clear: bridge is local, relay agent connects out, control-plane routes requests.
When not to use it
- →When the task does not involve relay/control-plane behavior, bridge-managed RPCs, or desktop-agent forwarding.
- →When the change destabilizes the browser contract or bridge session lifecycle.
- →When the task explicitly changes `/api/mobile/*` and `/v1/sessions/*` compatibility.
Limitations
- →Requires reading `.codex/rules/bridge-and-relay.md`.
- →Preserves `/api/mobile/*` and `/v1/sessions/*` compatibility by default.
- →Normalizes structured errors instead of leaking raw process failures.
How it compares
This skill provides a structured approach to modifying bridge-related components, ensuring compatibility and proper segregation of responsibilities, which is more controlled than ad-hoc changes.
Compared to similar skills
bridge-handler-task side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| bridge-handler-task (this skill) | 0 | 4mo | No flags | Advanced |
| architecture-patterns | 55 | 2mo | No flags | Advanced |
| kotlin-multiplatform | 32 | 3mo | Review | Advanced |
| nodejs-best-practices | 28 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
kotlin-multiplatform
vitorpamplona
Platform abstraction decision-making for Amethyst KMP project. Guides when to abstract vs keep platform-specific, source set placement (commonMain, jvmAndroid, platform-specific), expect/actual patterns. Covers primary targets (Android, JVM/Desktop, iOS) with web/wasm future considerations. Integrates with gradle-expert for dependency issues. Triggers on: abstraction decisions ("should I share this?"), source set placement questions, expect/actual creation, build.gradle.kts work, incorrect placement detection, KMP dependency suggestions.
nodejs-best-practices
davila7
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
workflow-orchestration-patterns
wshobson
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
java-pro
sickn33
Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.
arm-cortex-expert
sickn33
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.