What problem does it solve? Reimplementing hardware drivers in a differently-licensed OS requires understanding how Linux, Trusted Firmware-A, or vendor firmware drives a peripheral, but reading that GPL-licensed source directly risks contaminating the new implementation. This Skill acts as a research subagent that reads the encumbered source and returns only facts and mechanism descriptions, never code. ## Core Features & Use Cases - Clean-room reporting: Returns hardware facts (addresses, IRQs, clocks, register fields) and mechanism prose with every fact tagged by provenance class ([databook], [standard], [DT], [source-observed]). - Mechanical leak scanning: Ships scripts/leak_scan.py, a stdlib-only Python scanner that detects shared token runs and identifier reuse between a draft report and the encumbered source tree. - Subagent delegation model: Designed to run as a separate investigator agent so the code-writing context never touches encumbered source, with pinned-commit provenance for later verification. - Use Case: While porting a USB controller driver to a new RTOS, ask the investigator what MMIO base address, IRQ number, and init sequence the Linux dwc3 driver uses on your board, and receive a tagged, source-free report pinned to an exact kernel commit. ## Quick Start Ask the investigator subagent how the Linux kernel initializes a specific peripheral on your board and request a clean-room report with provenance tags.
