Hardware Test and Triage

{
  "slug": "hardware-test-and-triage",
  "title": "Hardware Test and Triage",
  "type": "skill",
  "version": "1.0.0",
  "description": "Agent skill: bench methodology for hardware test campaigns \u2014 writing and hardening test procedures against live bench results, triaging failures to root cause (hardware vs firmware vs config vs observation error), reading failure signatures, designing discriminating tests, and the document ledger that keeps a multi-day campaign coherent. Distilled from the Control Panel V2.0.1 Test 0.0 campaign.",
  "tags": [
    "skill",
    "hardware",
    "bench-test",
    "bring-up",
    "triage",
    "methodology",
    "test-procedure"
  ],
  "discovery_triggers": [
    "bench test",
    "test procedure",
    "board bring-up",
    "triage this failure",
    "root cause",
    "hardware test campaign",
    "why is this failing",
    "errata"
  ],
  "discovery_pitch": "Field-proven bench methodology for AI agents: the document ledger, verify-before-trusting, a failure-signature table, discriminating tests, observation-channel skepticism, bench safety rules, procedure-writing standards, test-firmware patterns, root-cause honesty, and the run-conclusion evidence merge.",
  "sample_prompts": [
    {
      "label": "Example",
      "prompt": "The RP2350 on the bench reads 'cannot read IDR' over SWD \u2014 triage this failure."
    }
  ],
  "scripts": {
    "install": "./install.sh",
    "uninstall": "./uninstall.sh"
  },
  "hero": {
    "headline": "Evidence beats recall on the bench",
    "subhead": "A field-proven methodology skill for hardware test campaigns: document ledger, failure signatures, discriminating tests, and root-cause honesty.",
    "screenshot": "docs/hero.png"
  },
  "dependencies": {}
}