skills.rest
haolange
haolangeCOMMUNITY
Explore all skills by this author →
GitHub

driver-device

Perform broker-mediated cross-device driver attribution checks with platform-specific validation.

15|5|Updated Mar 5, 2026
Search Tags:#multi-agent#device#attribution#driver#broker#rdc-debugger
One-click install
npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill driver-device
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: driver-device
Source: https://github.com/haolange/RDC-Agent-Frameworks/tree/main/debugger/platforms/claude-code/.claude/skills/driver-device
Command: npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill driver-device

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about driver-device

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform cross-device driver attribution for runtime failures?▼

Cross-device driver attribution identifies specific drivers, platforms, or device states causing runtime failures. You execute this check via rdc-debugger dispatch to investigate device-driver mismatches across distributed environments while maintaining broker-controlled safety gates.

What is broker-mediated live access for driver diagnostics?▼

Broker-mediated live access requires a broker to validate intake_gate.yaml and runtime broker artifacts before investigating live systems. This mechanism enforces the single_runtime_single_context policy and prohibits direct live CLI or persistent runtime handle reuse to ensure safe driver attribution.

When do I need cross-device attribution checks for platform-specific driver incompatibilities?▼

You need cross-device attribution checks when a distributed test run shows device-driver mismatches across environments. These checks enforce platform contract parameters like staged_handoff and multi_agent orchestration to safely attribute runtime failures to specific drivers or platforms.

Can I use direct CLI access to investigate runtime driver issues?▼

No, direct live CLI access and persistent runtime handle reuse are strictly prohibited. You must use broker-mediated actions that validate intake_gate.yaml and runtime broker artifacts before any live investigation of platform-specific driver incompatibilities.

How do I dispatch a multi-agent investigation for device-driver mismatches?▼

You dispatch a multi-agent investigation by invoking rdc-debugger to run a broker-mediated cross-device driver attribution check on the failing session. The validated investigation report is then directed into the platform-local workspace for specialist assignment.

Related Skills

Explore More Software Engineering Skills→
haolangehaolange
15

capture-repro

Creates deterministic capture baselines and environment snapshots for runtime debugging.

Community
Advanced
haolangehaolange
15

report-knowledge-curator

Generate BugFull and BugCard outputs and curate reusable knowledge for Claude Code workflows.

Community
Advanced
haolangehaolange
15

triage-taxonomy

Match bug descriptions to BugCard and BugFull history and map symptoms to taxonomy tags.

Community
Advanced
haolangehaolange
15

shader-ir

Parse HLSL, GLSL, and SPIR-V to detect suspicious shader fingerprints.

Community
Advanced