What's inside

One SKILL.md (the playbook) + one starter template. A preview:

Matter/Thread Rollout Planner

When to use

• You bought (or plan to buy) a smart-home hub with Matter and Thread and want the rollout to work the first time.
• Your current setup is a mess of Wi-Fi devices, old Zigbee gear, and three competing apps.
• You're deciding which existing devices survive the migration and which get replaced.
• You're an installer scoping a job and need a coverage plan you can defend.

Workflow

1. Draw the house (input: floor plan or room list → output: coverage map)
   Sketch every floor with room names and approximate distances. Mark: where the hub will live, where Wi-Fi is already weak (dead zones become Thread dead zones too if you don't plan), and physical barriers (brick, concrete, metal doors, mirrors) that eat 2.4 GHz signal. Thread runs on 2.4 GHz mesh — walls matter more than marketing suggests.
2. Place the border routers (input: coverage map → output: router placement)
   A Thread Border Router bridges Thread to your Wi-Fi/LAN. Rule of thumb: one border router per floor for a typical home, no device more than two hops from a router, and routers placed centrally — not in a closet, not behind the TV. If your hub is the only border router and it lives in the living room, the far bedroom's Thread lock is a gamble: add a second router (many smart speakers and TVs now include one) or move the hub.
3. Inventory by radio (input: device list → output: migration table)
   List every smart device and tag its radio: Matter-over-Thread, Matter-over-Wi-Fi, Zigbee (needs its own bridge or replacement), Z-Wave (same), Wi-Fi-proprietary (check for Matter firmware updates — several vendors shipped them), Bluetooth-only (range-limited, hub won't fix it). For each non-Matter device decide: keep via bridge, update firmware, or replace — with a cost per row.
4. Sequence the migration (input: migration table → output: rollout order)
   Order: (a) hub + border routers first, verify the mesh; (b) mains-powered Thread devices next (they become routers and strengthen the mesh — battery devices can't); (c) battery devices and locks; (d) automations and scenes last, rebuilt natively rather than imported. Never migrate everything Saturday morning — one room per evening, with a rollback note per room (what the old setup was).
5. Rebuild automations natively (input: old automations → output: new automation list)
   Don't port old routines 1:1 — re-express each in the hub's model: triggers (sensor, time, presence, alarm-sound recognition), conditions (who's home, which recognition tier), actions (device states, announcements). Kill every automation you can't explain in one sentence; each surviving one gets a name, a trigger, and a "what if the internet dies" answer (local-first automations keep working — cloud ones don't).
6. Document and harden (input: finished rollout → output: home network doc)
   Write the one-page doc: hub location and admin account, border router list, device inventory with radios, the Wi-Fi network IoT devices use (separate IoT SSID or VLAN if you can), and the recovery procedure (hub factory reset → what must be re-paired). Store it where the next person to touch the system will find it.

Template preview

Matter/Thread Rollout Worksheet

Plan with your AI before buying a single device.

1. Coverage map

Rooms per floor, distances, barriers (brick/concrete/metal/mirrors), Wi-Fi dead zones, planned hub location:

2. Border router placement

Two-hop check: is any Thread device more than 2 hops from a router? Fix now.

3. Device inventory by radio

4. Rollout order

1. Hub + border routers → verify mesh:
2. Mains-powered Thread devices (mesh backbone):
3. Battery devices & locks:
4. Automations rebuilt natively:
5. Old bridge decommissioned (after 1 clean week):

Rollback note per room:

5. Automations (rebuilt, not ported)

Buy the full skill pack — $4.99 Pro — all 511 skills