[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASYMHZGZA3BZX3ZNT18VPP":3,"skill-same:01M7ASYMHZGZA3BZX3ZNT18VPP":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASYMHZGZA3BZX3ZNT18VPP","wireless-thread-matter-lora-cellular-uwb-and-choosing",null,"Use when selecting a radio technology: Thread, Zigbee and Matter and what Matter actually standardises, LoRa and LPWAN with their duty-cycle and payload constraints, cellular and cellular IoT including LTE-M and NB-IoT, UWB for ranging, the other technologies worth knowing, and a direct method for choosing a radio from range, rate, power and cost requirements.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwireless-technologies-and-rf-engineering\u002Fskills\u002Fwireless-thread-matter-lora-cellular-uwb-and-choosing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wireless-thread-matter-lora-cellular-uwb-and-choosing\ndescription: \"Use when selecting a radio technology: Thread, Zigbee and Matter and what Matter actually standardises, LoRa and LPWAN with their duty-cycle and payload constraints, cellular and cellular IoT including LTE-M and NB-IoT, UWB for ranging, the other technologies worth knowing, and a direct method for choosing a radio from range, rate, power and cost requirements.\"\n---\n\n# Wireless Technologies and RF: Thread, Zigbee and Matter, LoRa and LPWAN, Cellular and Cellular IoT, UWB, Other Technologies, and Choosing a Radio\n\n> **Part 3 of 6** of the *Wireless Technologies: RF, Standards, Building and Programming* reference (plugin `wireless-technologies-and-rf-engineering`), covering §11–§16. Sibling skills: `wireless-propagation-link-budget-modulation-antennas-and-spectrum` (§0–§5), `wireless-wifi-bluetooth-ble-nfc-and-rfid` (§6–§10), `wireless-antenna-integration-certification-low-power-and-debugging` (§17–§21), `wireless-security-coexistence-and-positioning` (§22–§24), `wireless-reference` (§25–§30). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The physics is permanent and the mature standards are stable. Two areas are moving. See §25 → `wireless-reference` for Wi-Fi's next generation, and Bluetooth ranging.\n\n> **⚠️ The domain where physics imposes limits that no amount of software cleverness\n> removes — and where nearly every practical problem turns out to be either a link budget\n> problem, an antenna problem, or a coexistence problem.**\n>\n> **Builds on an electromagnetism reference (fields, propagation, transmission lines) and\n> complements a peripherals reference (§5's wireless HID), a computer-hardware reference\n> (§9 → `wireless-wifi-bluetooth-ble-nfc-and-rfid` networking), and a cryptography reference (WPA3, pairing, key exchange).**\n>\n> **⚠️ GOTCHA** boxes mark where spec-sheet numbers and field reality diverge — which in RF\n> is nearly everywhere.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ THE LINK BUDGET IS THE WHOLE GAME** (§2 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`). **Transmit power, antenna gains, path\n>    loss and receiver sensitivity determine whether a link works. Everything else is\n>    optimization within that envelope, and \"add more power\" is almost never the available\n>    lever because regulation caps it.**\n> 2. **⚠️ SPECTRUM IS A SHARED, CONTESTED, REGULATED RESOURCE** (§5 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`, §23 → `wireless-security-coexistence-and-positioning`). **You do not own\n>    your channel. Unlicensed bands mean your neighbours, your own other radios, and\n>    physically unrelated devices all degrade you — and coexistence design is not optional.**\n> 3. **⚠️ THE ANTENNA IS THE MOST NEGLECTED COMPONENT AND THE MOST DECISIVE** (§4 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`, §17 → `wireless-antenna-integration-certification-low-power-and-debugging`).\n>    **A superb radio with a badly integrated antenna performs worse than a mediocre radio\n>    with a good one, and antenna problems are usually designed in months before anyone\n>    measures them.**\n\n---\n\n## §11. Thread, Zigbee and Matter\n\n**⚠️ 802.15.4** is the shared PHY\u002FMAC underneath — ⚠️ **low rate, low power, mesh-capable,\n2.4 GHz (and sub-GHz variants).**\n**⚠️ Zigbee** adds its own network and application layers, ⚠️ **and its historical problem\nwas profile fragmentation between vendors.**\n**⚠️ Thread** is IPv6-native (6LoWPAN), ⚠️ **self-healing mesh, no single point of failure,\nwith Border Routers connecting to the wider IP network — and being IP-native is the\narchitectural advantage over Zigbee.**\n**⚠️ MATTER** is an APPLICATION layer running over Thread, Wi-Fi or Ethernet — ⚠️ **it is\nexplicitly NOT a radio standard, which is the single most common misunderstanding about\nit.**\n> **⚠️ GOTCHA — Matter's promise was \"everything works with everything,\" and the honest\n> assessment is that it has been slower and messier than promised.** ⚠️ **Feature coverage\n> lags device categories, vendor implementations differ, and multi-admin sharing has been\n> awkward.** **⚠️ It is real and improving; treat maturity claims by device category rather\n> than as a blanket.**\n\n**⚠️ Mesh routing realities**: ⚠️ **battery devices are usually END DEVICES that do not\nroute, so a mesh only heals if enough mains-powered routers exist — a mesh of battery\nsensors is not a mesh.**\n\n---\n\n## §12. LoRa and LPWAN\n\n**⚠️ LoRa is the modulation** (⚠️ **chirp spread spectrum — the reason it demodulates\nsignals BELOW the noise floor, which is genuinely remarkable**); ⚠️ **LoRaWAN is the network\nprotocol above it.**\n**⚠️ The trade is explicit**: ⚠️ **kilometres of range and years of battery, in exchange for\ntiny payloads, high latency and very low duty cycle.**\n**⚠️ Spreading factor** trades range against airtime — ⚠️ **and higher SF means much longer\ntransmissions, which consumes duty-cycle allowance and capacity fast.**\n**⚠️ Device classes**: ⚠️ **A (uplink-initiated, lowest power), B (scheduled receive slots),\nC (continuous receive, mains power).**\n**⚠️ Deployment models**: ⚠️ **private gateway versus public network versus roaming — and\nthe honest question for any LPWAN project is who owns and maintains the gateways.**\n**⚠️ The alternatives**: ⚠️ **Sigfox, Wi-Fi HaLow (802.11ah), Amazon Sidewalk, and\ncellular NB-IoT\u002FLTE-M** (§13).\n\n---\n\n## §13. Cellular and Cellular IoT\n\n**⚠️ The generations**: ⚠️ **and note 2G\u002F3G SUNSET has stranded a great deal of deployed\ntelemetry — a live lesson about designing hardware around a network you don't control.**\n**⚠️ 5G's three service classes** are the useful framing: ⚠️ **eMBB (bandwidth), URLLC\n(latency and reliability), mMTC (device density) — and no deployment delivers all three at\nonce.**\n**⚠️ mmWave versus sub-6 GHz** is §2 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`'s physics again: ⚠️ **enormous bandwidth, terrible\npropagation and building penetration, which is why mmWave coverage is patchy and sub-6 does\nthe real work.**\n**⚠️ For IoT specifically**: ⚠️ **NB-IoT (deep indoor penetration, tiny data) and LTE-M\n(more bandwidth, mobility, VoLTE) — with PSM and eDRX as the power-saving mechanisms that\nmake multi-year battery life possible on a cellular radio.**\n**⚠️ Practical concerns**: ⚠️ **eSIM\u002FiSIM provisioning, roaming agreements and permanent\nroaming restrictions, module certification against carrier requirements (⚠️ which is\nseparate from and additional to regulatory certification, §18 → `wireless-antenna-integration-certification-low-power-and-debugging`), and network sunset risk.**\n\n---\n\n## §14. UWB\n\n**⚠️ Ultra-wideband** transmits extremely short pulses across very wide bandwidth at very\nlow power spectral density.\n**⚠️ Why it is good at ranging**: ⚠️ **time-of-flight resolution scales with BANDWIDTH, and\nUWB has a great deal of it — giving roughly 10 cm accuracy — plus the short pulse makes\nmultipath separable rather than confusing.**\n**⚠️ The security property is the important one**: ⚠️ **cryptographically timed\nDISTANCE BOUNDING resists relay attacks in a way RSSI-based proximity fundamentally cannot**\n(§22 → `wireless-security-coexistence-and-positioning`, §24 → `wireless-security-coexistence-and-positioning`).\n**⚠️ Standards**: ⚠️ **802.15.4z, with FiRa and CCC (Car Connectivity Consortium) driving\ninteroperability for digital car keys.**\n**⚠️ The cost**: ⚠️ **dedicated hardware and meaningfully higher power than BLE — which is\nexactly the pressure that produced Bluetooth Channel Sounding** (§25.2 → `wireless-reference`).\n\n---\n\n## §15. Other Technologies Worth Knowing\n\n**⚠️ Wi-Fi HaLow (802.11ah)** — ⚠️ **sub-GHz Wi-Fi, kilometre range, IP-native, low rate;\ntechnically attractive and adoption has been slow.**\n**⚠️ 60 GHz (802.11ad\u002Fay, WiGig)** — ⚠️ **multi-gigabit at room scale, blocked by a hand.**\n**⚠️ Satellite**: ⚠️ **LEO constellations, and direct-to-device messaging now appearing in\nphones — with latency and link budget both governed by §2 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`.**\n**⚠️ Infrared** — ⚠️ **still ubiquitous in remotes, line-of-sight, no spectrum regulation.**\n**⚠️ Wireless power (Qi)** — ⚠️ **inductive coupling like NFC (§10 → `wireless-wifi-bluetooth-ble-nfc-and-rfid`), with alignment and\nforeign-object detection as the engineering problems.**\n**⚠️ Wired alternatives worth remembering**: ⚠️ **Ethernet and PoE solve many \"IoT\"\nproblems better than any radio, and powerline and MoCA exist — the best wireless decision\nis sometimes not to.**\n\n---\n\n# PART III — BUILDING WIRELESS PRODUCTS\n\n## §16. Choosing a Radio\n\n```\n⚠️ THE DECISION ORDER — ⚠️ answer these before picking a chip\n   ⚠️ 1. RANGE and environment · 2. DATA RATE and duty cycle ·\n   ⚠️ 3. POWER SOURCE — battery life target is the harshest\n      constraint and drives everything (§19)\n   ⚠️ 4. Latency requirement · 5. Number of nodes and topology ·\n   ⚠️ 6. What must it talk TO? (⚠️ if a phone must connect\n      directly, that means BLE or Wi-Fi, full stop)\n   ⚠️ 7. Infrastructure — does a gateway exist? · 8. Regions to sell\n⚠️ MODULE vs CHIP-DOWN\n   ⚠️ PRE-CERTIFIED MODULE  ⚠️ dramatically cheaper and faster for\n      low and medium volume, because it carries modular\n      certification (§18). ⚠️ Higher unit cost\n   ⚠️ CHIP-DOWN  cheapest at volume, ⚠️ full certification burden\n      and RF layout expertise required\n   ⚠️ ⚠️ FOR MOST PROJECTS, USE A MODULE. The certification saving\n      alone usually exceeds the unit-cost penalty\n⚠️ ECOSYSTEM MATTERS AS MUCH AS SILICON  ⚠️ SDK quality,\n   documentation, stack maturity, long-term availability, and\n   whether you can get support\n```\n","# Wireless Technologies and RF: Thread, Zigbee and Matter, LoRa and LPWAN, Cellular and Cellular IoT, UWB, Other Technologies, and Choosing a Radio\n\n> **Part 3 of 6** of the *Wireless Technologies: RF, Standards, Building and Programming* reference (plugin `wireless-technologies-and-rf-engineering`), covering §11–§16. Sibling skills: `wireless-propagation-link-budget-modulation-antennas-and-spectrum` (§0–§5), `wireless-wifi-bluetooth-ble-nfc-and-rfid` (§6–§10), `wireless-antenna-integration-certification-low-power-and-debugging` (§17–§21), `wireless-security-coexistence-and-positioning` (§22–§24), `wireless-reference` (§25–§30). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The physics is permanent and the mature standards are stable. Two areas are moving. See §25 → `wireless-reference` for Wi-Fi's next generation, and Bluetooth ranging.\n\n> **⚠️ The domain where physics imposes limits that no amount of software cleverness\n> removes — and where nearly every practical problem turns out to be either a link budget\n> problem, an antenna problem, or a coexistence problem.**\n>\n> **Builds on an electromagnetism reference (fields, propagation, transmission lines) and\n> complements a peripherals reference (§5's wireless HID), a computer-hardware reference\n> (§9 → `wireless-wifi-bluetooth-ble-nfc-and-rfid` networking), and a cryptography reference (WPA3, pairing, key exchange).**\n>\n> **⚠️ GOTCHA** boxes mark where spec-sheet numbers and field reality diverge — which in RF\n> is nearly everywhere.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ THE LINK BUDGET IS THE WHOLE GAME** (§2 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`). **Transmit power, antenna gains, path\n>    loss and receiver sensitivity determine whether a link works. Everything else is\n>    optimization within that envelope, and \"add more power\" is almost never the available\n>    lever because regulation caps it.**\n> 2. **⚠️ SPECTRUM IS A SHARED, CONTESTED, REGULATED RESOURCE** (§5 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`, §23 → `wireless-security-coexistence-and-positioning`). **You do not own\n>    your channel. Unlicensed bands mean your neighbours, your own other radios, and\n>    physically unrelated devices all degrade you — and coexistence design is not optional.**\n> 3. **⚠️ THE ANTENNA IS THE MOST NEGLECTED COMPONENT AND THE MOST DECISIVE** (§4 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`, §17 → `wireless-antenna-integration-certification-low-power-and-debugging`).\n>    **A superb radio with a badly integrated antenna performs worse than a mediocre radio\n>    with a good one, and antenna problems are usually designed in months before anyone\n>    measures them.**\n\n---\n\n## §11. Thread, Zigbee and Matter\n\n**⚠️ 802.15.4** is the shared PHY\u002FMAC underneath — ⚠️ **low rate, low power, mesh-capable,\n2.4 GHz (and sub-GHz variants).**\n**⚠️ Zigbee** adds its own network and application layers, ⚠️ **and its historical problem\nwas profile fragmentation between vendors.**\n**⚠️ Thread** is IPv6-native (6LoWPAN), ⚠️ **self-healing mesh, no single point of failure,\nwith Border Routers connecting to the wider IP network — and being IP-native is the\narchitectural advantage over Zigbee.**\n**⚠️ MATTER** is an APPLICATION layer running over Thread, Wi-Fi or Ethernet — ⚠️ **it is\nexplicitly NOT a radio standard, which is the single most common misunderstanding about\nit.**\n> **⚠️ GOTCHA — Matter's promise was \"everything works with everything,\" and the honest\n> assessment is that it has been slower and messier than promised.** ⚠️ **Feature coverage\n> lags device categories, vendor implementations differ, and multi-admin sharing has been\n> awkward.** **⚠️ It is real and improving; treat maturity claims by device category rather\n> than as a blanket.**\n\n**⚠️ Mesh routing realities**: ⚠️ **battery devices are usually END DEVICES that do not\nroute, so a mesh only heals if enough mains-powered routers exist — a mesh of battery\nsensors is not a mesh.**\n\n---\n\n## §12. LoRa and LPWAN\n\n**⚠️ LoRa is the modulation** (⚠️ **chirp spread spectrum — the reason it demodulates\nsignals BELOW the noise floor, which is genuinely remarkable**); ⚠️ **LoRaWAN is the network\nprotocol above it.**\n**⚠️ The trade is explicit**: ⚠️ **kilometres of range and years of battery, in exchange for\ntiny payloads, high latency and very low duty cycle.**\n**⚠️ Spreading factor** trades range against airtime — ⚠️ **and higher SF means much longer\ntransmissions, which consumes duty-cycle allowance and capacity fast.**\n**⚠️ Device classes**: ⚠️ **A (uplink-initiated, lowest power), B (scheduled receive slots),\nC (continuous receive, mains power).**\n**⚠️ Deployment models**: ⚠️ **private gateway versus public network versus roaming — and\nthe honest question for any LPWAN project is who owns and maintains the gateways.**\n**⚠️ The alternatives**: ⚠️ **Sigfox, Wi-Fi HaLow (802.11ah), Amazon Sidewalk, and\ncellular NB-IoT\u002FLTE-M** (§13).\n\n---\n\n## §13. Cellular and Cellular IoT\n\n**⚠️ The generations**: ⚠️ **and note 2G\u002F3G SUNSET has stranded a great deal of deployed\ntelemetry — a live lesson about designing hardware around a network you don't control.**\n**⚠️ 5G's three service classes** are the useful framing: ⚠️ **eMBB (bandwidth), URLLC\n(latency and reliability), mMTC (device density) — and no deployment delivers all three at\nonce.**\n**⚠️ mmWave versus sub-6 GHz** is §2 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`'s physics again: ⚠️ **enormous bandwidth, terrible\npropagation and building penetration, which is why mmWave coverage is patchy and sub-6 does\nthe real work.**\n**⚠️ For IoT specifically**: ⚠️ **NB-IoT (deep indoor penetration, tiny data) and LTE-M\n(more bandwidth, mobility, VoLTE) — with PSM and eDRX as the power-saving mechanisms that\nmake multi-year battery life possible on a cellular radio.**\n**⚠️ Practical concerns**: ⚠️ **eSIM\u002FiSIM provisioning, roaming agreements and permanent\nroaming restrictions, module certification against carrier requirements (⚠️ which is\nseparate from and additional to regulatory certification, §18 → `wireless-antenna-integration-certification-low-power-and-debugging`), and network sunset risk.**\n\n---\n\n## §14. UWB\n\n**⚠️ Ultra-wideband** transmits extremely short pulses across very wide bandwidth at very\nlow power spectral density.\n**⚠️ Why it is good at ranging**: ⚠️ **time-of-flight resolution scales with BANDWIDTH, and\nUWB has a great deal of it — giving roughly 10 cm accuracy — plus the short pulse makes\nmultipath separable rather than confusing.**\n**⚠️ The security property is the important one**: ⚠️ **cryptographically timed\nDISTANCE BOUNDING resists relay attacks in a way RSSI-based proximity fundamentally cannot**\n(§22 → `wireless-security-coexistence-and-positioning`, §24 → `wireless-security-coexistence-and-positioning`).\n**⚠️ Standards**: ⚠️ **802.15.4z, with FiRa and CCC (Car Connectivity Consortium) driving\ninteroperability for digital car keys.**\n**⚠️ The cost**: ⚠️ **dedicated hardware and meaningfully higher power than BLE — which is\nexactly the pressure that produced Bluetooth Channel Sounding** (§25.2 → `wireless-reference`).\n\n---\n\n## §15. Other Technologies Worth Knowing\n\n**⚠️ Wi-Fi HaLow (802.11ah)** — ⚠️ **sub-GHz Wi-Fi, kilometre range, IP-native, low rate;\ntechnically attractive and adoption has been slow.**\n**⚠️ 60 GHz (802.11ad\u002Fay, WiGig)** — ⚠️ **multi-gigabit at room scale, blocked by a hand.**\n**⚠️ Satellite**: ⚠️ **LEO constellations, and direct-to-device messaging now appearing in\nphones — with latency and link budget both governed by §2 → `wireless-propagation-link-budget-modulation-antennas-and-spectrum`.**\n**⚠️ Infrared** — ⚠️ **still ubiquitous in remotes, line-of-sight, no spectrum regulation.**\n**⚠️ Wireless power (Qi)** — ⚠️ **inductive coupling like NFC (§10 → `wireless-wifi-bluetooth-ble-nfc-and-rfid`), with alignment and\nforeign-object detection as the engineering problems.**\n**⚠️ Wired alternatives worth remembering**: ⚠️ **Ethernet and PoE solve many \"IoT\"\nproblems better than any radio, and powerline and MoCA exist — the best wireless decision\nis sometimes not to.**\n\n---\n\n# PART III — BUILDING WIRELESS PRODUCTS\n\n## §16. Choosing a Radio\n\n```\n⚠️ THE DECISION ORDER — ⚠️ answer these before picking a chip\n   ⚠️ 1. RANGE and environment · 2. DATA RATE and duty cycle ·\n   ⚠️ 3. POWER SOURCE — battery life target is the harshest\n      constraint and drives everything (§19)\n   ⚠️ 4. Latency requirement · 5. Number of nodes and topology ·\n   ⚠️ 6. What must it talk TO? (⚠️ if a phone must connect\n      directly, that means BLE or Wi-Fi, full stop)\n   ⚠️ 7. Infrastructure — does a gateway exist? · 8. Regions to sell\n⚠️ MODULE vs CHIP-DOWN\n   ⚠️ PRE-CERTIFIED MODULE  ⚠️ dramatically cheaper and faster for\n      low and medium volume, because it carries modular\n      certification (§18). ⚠️ Higher unit cost\n   ⚠️ CHIP-DOWN  cheapest at volume, ⚠️ full certification burden\n      and RF layout expertise required\n   ⚠️ ⚠️ FOR MOST PROJECTS, USE A MODULE. The certification saving\n      alone usually exceeds the unit-cost penalty\n⚠️ ECOSYSTEM MATTERS AS MUCH AS SILICON  ⚠️ SDK quality,\n   documentation, stack maturity, long-term availability, and\n   whether you can get support\n```\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwireless-technologies-and-rf-engineering\u002Fskills\u002Fwireless-thread-matter-lora-cellular-uwb-and-choosing",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill wireless-thread-matter-lora-cellular-uwb-and-choosing",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill wireless-thread-matter-lora-cellular-uwb-and-choosing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill wireless-thread-matter-lora-cellular-uwb-and-choosing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwireless-technologies-and-rf-engineering\u002Fskills\u002Fwireless-thread-matter-lora-cellular-uwb-and-choosing\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]