tapo: Skill for Claude Code

Verify Device Support

Device support is stated in many places and none of them is generated from the others. This skill checks that they all agree with the code, which is the source of truth:

• DeviceType::from_model in tapo/src/api/discovery/device_type.rs says which model strings the library knows and which category each belongs to
• DiscoveryResult::new in tapo/src/api/discovery/discovery_result.rs says which handler each category gets
• the model match in tapo/src/responses/child_device_list_hub_result/child_device_hub_result.rs says which hub child models are decoded, and so which child handler each gets
• each handler's pub methods (explicit ones plus the ones tapo_handler!, tapo_child_handler! and hub_child_handlers! generate) say what it can do, and #[cfg(feature = "debug")] says which of them need the debug feature

Run the whole skill whenever a device model is added or removed, a handler gains or loses a method, a method's debug gating changes, or on request. On its own, this skill reports and does not change anything. When /pre-commit invokes it, or the user asked for the findings to be fixed, fix every finding, rerun the script until it exits 0, and report what was changed. Never post anywhere.

Step 1: Run the mechanical checks

python -I .claude/skills/verify-device-support/scripts/device_inventory.py

The script reads the sources above and compares them with every documentation surface listed in Step 2. It prints one line per mismatch, prefixed with the check that found it, and exits 1 when there are any. Lines prefixed note: are not findings. They point at wording that is a superset of what the code serves (a shared device-info type, the camera doc naming untested models, a model alias the device reports) and need a human decision, which Step 3 covers.

If the script crashes or reports that it cannot find a handler, a table column, or a mapping, the code moved in a way the script does not understand. Fix the script in the same change, then rerun it. Do not work around it by reading the files by hand only; the script is what keeps the next run honest.