agents: state the codex bridge's contract in its description The description a selector reads said only "Bridge one structured code-verifier task to Codex" — nothing about what goes in, what comes back, or why to pick it over code-verifier, which is the one distinction that matters between the two. Say the contract instead, avoiding ": " so strict YAML parsers accept the frontmatter. The usbmon description loses its trailing list of example phrasings; its first sentence already names those intents, and descriptions are paid for on every request.
diff --git a/.claude/agents/codex-code-verifier.md b/.claude/agents/codex-code-verifier.md index d2e632d..3a78d00 100644 --- a/.claude/agents/codex-code-verifier.md +++ b/.claude/agents/codex-code-verifier.md
@@ -1,6 +1,6 @@ --- name: codex-code-verifier -description: Bridge one structured code-verifier task to Codex. Read-only. +description: Run one structured code-verifier task on Codex rather than Claude — a bridge only, taking JSON `prompt`+`schema` in, returning schema-valid JSON, read-only, failing rather than fabricating a result. Use `code-verifier` for the Claude-hosted equivalent. tools: Bash model: haiku effort: low
diff --git a/.claude/skills/usbmon/SKILL.md b/.claude/skills/usbmon/SKILL.md index 490c79e..a90744d 100644 --- a/.claude/skills/usbmon/SKILL.md +++ b/.claude/skills/usbmon/SKILL.md
@@ -1,6 +1,6 @@ --- name: usbmon -description: Use when capturing, analyzing, or debugging USB bus traffic on a link where a Linux PC is the host (TinyUSB in device role) — enumeration failures, STALLed control transfers, missing/short bulk or interrupt transfers, isochronous/audio dropouts, or descriptor problems. Captures host-side URBs with usbmon + tshark into a Wireshark pcapng and decodes them. Not applicable when TinyUSB is the host — no URBs traverse the PC (use usb-sniffer / target-debug). Use whenever you need to see what the Linux host actually exchanged with a device on real hardware, even if the user just says "sniff USB", "capture the enumeration", or "why won't my device enumerate". +description: Use when capturing, analyzing, or debugging USB bus traffic on a link where a Linux PC is the host (TinyUSB in device role) — enumeration failures, STALLed control transfers, missing/short bulk or interrupt transfers, isochronous/audio dropouts, or descriptor problems. Captures host-side URBs with usbmon + tshark into a Wireshark pcapng and decodes them. Not applicable when TinyUSB is the host — no URBs traverse the PC (use usb-sniffer / target-debug). Use it whenever you need to see what the Linux host actually exchanged with a device on real hardware. --- # usbmon — capture & debug USB traffic