driver-device

What problem does it solve?

This skill centralizes and standardizes cross-device driver and device attribution checks so engineers can safely investigate runtime driver issues and platform-specific incompatibilities without risking unsafe access to live systems.

Core Features & Use Cases

• Platform-aware Diagnostics: Enforces platform contract parameters such as staged_handoff, multi_agent orchestration, and single_runtime_single_context runtime policy.
• Safe Live Access Controls: Requires broker-mediated actions, validates intake_gate artifacts and runtime broker artifacts before any live investigation, and forbids direct live CLI or persistent runtime handle reuse.
• Operational Reporting: Directs all case artifacts and reports to the platform-local workspace and integrates with rdc-debugger dispatch for specialist assignment.
• Use Case: When a distributed test run shows device-driver mismatches across environments, invoke rdc-debugger to dispatch this skill to attribute the failure to specific drivers, platforms, or device states while maintaining broker-controlled safety gates.

Quick Start

Use the driver-device skill via rdc-debugger to run a broker-mediated cross-device driver attribution check on the failing session and write the validated investigation report into the platform-local workspace.