[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2T56746K17SYG97EP2X6P":3,"skill-same:01M7C2T56746K17SYG97EP2X6P":54},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M7C2T56746K17SYG97EP2X6P","mesh-onboard",null,"Bring a device into the fleet on the bench, coaching the person at the cable. Use when the operator has a new tracker or radio in hand, when a device must be read or exported before a change, or when a device that was managed has stopped answering over the air. Works through Mesh Manager's bench actions; every write is read back from the device.","MilUX-Ltd\u002Fmesh-manager","MilUX-Ltd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64754564?v=4","01M7C2SR5T2FRVMXJCEB1YZD7B","MilUX","01M7C2SR6EH5C6PW0W7YRF75TQ",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmesh-onboard\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mesh-onboard\ndescription: Bring a device into the fleet on the bench, coaching the person at the cable. Use when the operator has a new tracker or radio in hand, when a device must be read or exported before a change, or when a device that was managed has stopped answering over the air. Works through Mesh Manager's bench actions; every write is read back from the device.\naudited: 2026-09-12\naudit_verdict: pass with cautions\ncautions_accepted: 2026-09-12, Matt Odell, MilUX Ltd\naudited_with: skill-safety-audit (MilUX meta-skills)\naudit_sha: 7e03b1c5a4d62f88\nproduct_version: 1.6.1\norigin: mesh-manager\u002Fskills\nsource: MilUX Ltd\nmaintainer: MilUX Ltd\nlicense: GPL-3.0-or-later\ncategory: operations\n---\n\n# Onboarding on the bench\n\nLoad `mesh-lessons` first. The person is at the box with a cable; you are at the screen or\nthe connector. Say one step at a time and wait for what they see.\n\n## 1. Find the device\n\n`bench_devices`. It lists the USB devices by their by-id name, never the gateway's own radio.\nAsk the person to plug the device in if the list is empty, then read it again. A device\nmarked `bootloader` answers nothing: read them the `recovery` step and stop there until it\ncomes back as a normal port.\n\n## 2. Read it before you change it\n\n`bench_read` with the device's `path`. Say what it is: the names, hardware, `firmware`,\nregion and preset, `role`, its channels by name, and whether it is `managed` (this radio's\nkey among its `admin_keys`). If it holds three foreign admin keys, onboarding will be\nrefused; say so now, not after.\n\n## 3. Keep what it had\n\n`bench_export` with the `path`. The export lands on the box, keys included, at a path the\nanswer names; nothing of it comes back to you, and you never ask for its content.\n\n## 4. Onboard\n\nAgree the `long_name` (up to 39 bytes), the `short_name` (4) and the `role` with the operator\nin their words, then `bench_onboard`. It writes the names and role, this radio's primary\nchannel and key, its region and preset, and this radio's public key as an admin key, and\nreads every one back from the device. Read the answer back to the person: `confirmed` true\nand what `read_back` says, or `unconfirmed` with the reason. Never say \"done\" for an\nunconfirmed write.\n\n## 5. Check the register\n\n`register`: the device now carries `managed` true and an `onboarded_at`. If the operator\nwants a `label` or a `holder` on it, `register_set`. The device is now one you can reach\nover the air (`mesh-operate`, step 6) once it is heard on the mesh.\n\n**If the fleet uses MQTT, this device does not have it yet.** Onboarding writes names, role,\nchannel, region and the admin key, and nothing about a broker. A device that needs it is a\nseparate write, and `mesh-join` says why the settings live on the radio and the box carries the\nconnection.\n\n## What you never do\n\nOpen the gateway's own radio from the bench, it is set from the Radio page. Read a key out\nof an export or an answer. Treat a name the device came with as anything but a label.\n","# Onboarding on the bench\n\nLoad `mesh-lessons` first. The person is at the box with a cable; you are at the screen or\nthe connector. Say one step at a time and wait for what they see.\n\n## 1. Find the device\n\n`bench_devices`. It lists the USB devices by their by-id name, never the gateway's own radio.\nAsk the person to plug the device in if the list is empty, then read it again. A device\nmarked `bootloader` answers nothing: read them the `recovery` step and stop there until it\ncomes back as a normal port.\n\n## 2. Read it before you change it\n\n`bench_read` with the device's `path`. Say what it is: the names, hardware, `firmware`,\nregion and preset, `role`, its channels by name, and whether it is `managed` (this radio's\nkey among its `admin_keys`). If it holds three foreign admin keys, onboarding will be\nrefused; say so now, not after.\n\n## 3. Keep what it had\n\n`bench_export` with the `path`. The export lands on the box, keys included, at a path the\nanswer names; nothing of it comes back to you, and you never ask for its content.\n\n## 4. Onboard\n\nAgree the `long_name` (up to 39 bytes), the `short_name` (4) and the `role` with the operator\nin their words, then `bench_onboard`. It writes the names and role, this radio's primary\nchannel and key, its region and preset, and this radio's public key as an admin key, and\nreads every one back from the device. Read the answer back to the person: `confirmed` true\nand what `read_back` says, or `unconfirmed` with the reason. Never say \"done\" for an\nunconfirmed write.\n\n## 5. Check the register\n\n`register`: the device now carries `managed` true and an `onboarded_at`. If the operator\nwants a `label` or a `holder` on it, `register_set`. The device is now one you can reach\nover the air (`mesh-operate`, step 6) once it is heard on the mesh.\n\n**If the fleet uses MQTT, this device does not have it yet.** Onboarding writes names, role,\nchannel, region and the admin key, and nothing about a broker. A device that needs it is a\nseparate write, and `mesh-join` says why the settings live on the radio and the box carries the\nconnection.\n\n## What you never do\n\nOpen the gateway's own radio from the bench, it is set from the Radio page. Read a key out\nof an export or an answer. Treat a name the device came with as anything but a label.\n",{"name":5,"origin":24,"source":25,"audited":26,"license":27,"category":28,"audit_sha":29,"maintainer":25,"description":7,"audited_with":30,"audit_verdict":31,"product_version":32,"cautions_accepted":33},"mesh-manager\u002Fskills","MilUX Ltd",1789171200000,"GPL-3.0-or-later","operations","7e03b1c5a4d62f88","skill-safety-audit (MilUX meta-skills)","pass with cautions","1.6.1","2026-09-12, Matt Odell, MilUX Ltd","main","e36ec374e05e01a3701b748f80e27ef7fdab4613","plugin\u002Fskills\u002Fmesh-onboard","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd","2026-10-24 05:03:31",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add MilUX-Ltd\u002Fmesh-manager --skill mesh-onboard",{"tool":46,"command":47},"bunx","bunx skills add MilUX-Ltd\u002Fmesh-manager --skill mesh-onboard",{"tool":49,"command":50},"pnpm","pnpm dlx skills add MilUX-Ltd\u002Fmesh-manager --skill mesh-onboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmesh-onboard\u002FSKILL.md",true,[],[55,61,66,72,78,84],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7C2W3PHDDSA6HQEQ4FAV2F7","mesh-operate","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fsrc\u002Fmesh_manager\u002Fbrief\u002Fskills\u002Fmesh-operate\u002FSKILL.md",[],[],{"skillNo":62,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7C2W0X4TSSZ5K992AX1HM62","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fsrc\u002Fmesh_manager\u002Fbrief\u002Fskills\u002Fmesh-onboard\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7C2VYQEGP38R1HF6F0CXZZ8","mesh-lessons","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fsrc\u002Fmesh_manager\u002Fbrief\u002Fskills\u002Fmesh-lessons\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7C2VXEK56HN7ZRDXKGTZZ43","mesh-join","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fsrc\u002Fmesh_manager\u002Fbrief\u002Fskills\u002Fmesh-join\u002FSKILL.md",[],[],{"skillNo":79,"name":57,"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},"01M7C2VS7QBKTM3KZQ2Q8T59PE","Triage a Meshtastic mesh through Mesh Manager and prepare the fix to the gate. Use when the operator says the mesh is down, a tracker has vanished, nobody is getting messages, or before taking the kit somewhere new. Runs reads, asks the mesh what only the mesh can answer, and hands over the decision.","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmesh-operate\u002FSKILL.md",[],[],{"skillNo":85,"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":86,"categories":87,"keywords":88,"publishedAt":19},"01M7C2VMRR78NEDSBNED686991","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmesh-onboard\u002FSKILL.md",[],[]]