[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2VS7QBKTM3KZQ2Q8T59PE":3,"skill-same:01M7C2VS7QBKTM3KZQ2Q8T59PE":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},"01M7C2VS7QBKTM3KZQ2Q8T59PE","mesh-operate",null,"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.","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\u002Fskills\u002Fmesh-operate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mesh-operate\ndescription: 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.\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: 41ac7e0b96d8f215\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# Operating the mesh: triage to the gate\n\nLoad `mesh-lessons` first. Then work top down; stop at the first thing that explains the\nsymptom, and say what you did not check.\n\n## 1. What kind of box this is\n\n`status` carries `mode`. A `tak-server` box bridges into a TAK Server, a `server` box has no TAK\nat all, and a `desktop` box is a laptop with a radio in the USB port. Read it before anything\nelse, because it decides what \"working\" means here and which of the checks below apply. Proposing\nthat somebody check TAK on a box that has none wastes their time and tells them you did not look.\n\n## 2. The bridge and the radio\n\n`status`. In this order: `radio_present`, `bootloader`, `connected`, `watchdog`,\n`last_activity`, `last_forwarded`, `nodes_seen`. A false at the top explains everything below\nit; report that one line and the physical action it needs. On a `server` box `last_forwarded`\nis not a fault signal: there is nothing to forward to.\n\n## 3. Who is on the mesh, and how well\n\n`links`, which is `nodes` with the picture: `direct_snr` is the SNR of the last packet that\ncame straight from that node, the only figure that describes its link to this radio; `history`\nis the last two hundred readings, so a link getting worse shows before it fails. Split the\nnodes: heard here recently, heard here but stale, database only (`heard_here` false). A node\nat `hops` two or three is at the edge; a tracker at five per cent `battery` is about to leave.\nSay which nodes are which, by id and name. `route` gives the last traceroute answer for a\nnode, hop by hop with the SNR at each hop, `towards` and `back`.\n\n**Split off the ones that are not yours.** A node carrying `origin_name` came over a link from\nanother site; this radio never heard it. Report those separately and say which site, because they\nare not evidence about your own air and nobody can walk out and find them. `mesh-join` has the\nrest.\n\n## 4. What they ride\n\n`channels` and `config`: the primary channel, the region, the modem preset. If the operator's\nbrief (`mesh_context`) names a different region or channel, that is the finding.\n\n## 5. Ask the mesh, at propose or above\n\nOnly what changes nothing: `traceroute` to a node that should be there (the answer arrives as\na route; read it with `route`), `request_position` from a tracker with no fix. Say what you\nare sending and why first. Watch `log` and `messages` for the answer, and wait a minute\nbefore reading silence as a fault.\n\n## 6. What the fleet is, and what you may change on it\n\n`register`: every node the radio knows of joined with the box's register on radio id, the\noperator's `label` and `holder` beside the node's own name, and `managed`, which is true only\nwhen a read of the device itself showed this radio's public key among its admin keys. A\ndevice that is not managed cannot be changed from here at all; the only thing to say about\nit is \"bring it to the bench\". For a managed device, `node_read` asks it over the air for what\nit holds now; `node_set`, `node_set_region`, `node_channel_push` and `node_reboot` are the\nwrites, at `act` or through `propose`. Every write answers `confirmed` true only when the\ndevice's own answer matched; `unconfirmed` with a reason otherwise; a write over LoRa can\ntake a minute and silence is not failure. Region, slot 0 and reboot need `confirm` set to the\ndevice's own id, because afterwards it may be unreachable over the air.\n\n## 7. Hand over the decision\n\nAnything that would change a device, a channel or a region is above the on-air line unless\nyou hold `act`. Use\n`propose` with the exact action and arguments and a rationale in the operator's words, and\nsay what changes if they say yes and what the way back is. A region change before travel needs\ntwo QRs: one for the destination and one for the way home; say so.\n\n## Alerts, and what acknowledging does not mean\n\n`alerts` is what is open. At `act` you can `alert_ack`, and it is worth being exact about what\nthat does: it takes a row off the open list and stops it being raised again while the condition\nstill holds. **It does not fix anything and it does not mean the condition is fine.** When the\ncondition genuinely clears the acknowledgement is forgotten, so a recurrence alerts afresh.\nAcknowledge when the operator has decided they know, not to tidy a list you find untidy, and say\nwhich alerts you acknowledged. An alert that came over a link belongs to the site it came from\nand cannot be acknowledged here.\n\n## Before the kit goes somewhere new\n\nRead `config` for the region. Read the brief for where the kit is going. If they differ, the\nfirst proposal is the region, and nothing else until the operator answers.\n","# Operating the mesh: triage to the gate\n\nLoad `mesh-lessons` first. Then work top down; stop at the first thing that explains the\nsymptom, and say what you did not check.\n\n## 1. What kind of box this is\n\n`status` carries `mode`. A `tak-server` box bridges into a TAK Server, a `server` box has no TAK\nat all, and a `desktop` box is a laptop with a radio in the USB port. Read it before anything\nelse, because it decides what \"working\" means here and which of the checks below apply. Proposing\nthat somebody check TAK on a box that has none wastes their time and tells them you did not look.\n\n## 2. The bridge and the radio\n\n`status`. In this order: `radio_present`, `bootloader`, `connected`, `watchdog`,\n`last_activity`, `last_forwarded`, `nodes_seen`. A false at the top explains everything below\nit; report that one line and the physical action it needs. On a `server` box `last_forwarded`\nis not a fault signal: there is nothing to forward to.\n\n## 3. Who is on the mesh, and how well\n\n`links`, which is `nodes` with the picture: `direct_snr` is the SNR of the last packet that\ncame straight from that node, the only figure that describes its link to this radio; `history`\nis the last two hundred readings, so a link getting worse shows before it fails. Split the\nnodes: heard here recently, heard here but stale, database only (`heard_here` false). A node\nat `hops` two or three is at the edge; a tracker at five per cent `battery` is about to leave.\nSay which nodes are which, by id and name. `route` gives the last traceroute answer for a\nnode, hop by hop with the SNR at each hop, `towards` and `back`.\n\n**Split off the ones that are not yours.** A node carrying `origin_name` came over a link from\nanother site; this radio never heard it. Report those separately and say which site, because they\nare not evidence about your own air and nobody can walk out and find them. `mesh-join` has the\nrest.\n\n## 4. What they ride\n\n`channels` and `config`: the primary channel, the region, the modem preset. If the operator's\nbrief (`mesh_context`) names a different region or channel, that is the finding.\n\n## 5. Ask the mesh, at propose or above\n\nOnly what changes nothing: `traceroute` to a node that should be there (the answer arrives as\na route; read it with `route`), `request_position` from a tracker with no fix. Say what you\nare sending and why first. Watch `log` and `messages` for the answer, and wait a minute\nbefore reading silence as a fault.\n\n## 6. What the fleet is, and what you may change on it\n\n`register`: every node the radio knows of joined with the box's register on radio id, the\noperator's `label` and `holder` beside the node's own name, and `managed`, which is true only\nwhen a read of the device itself showed this radio's public key among its admin keys. A\ndevice that is not managed cannot be changed from here at all; the only thing to say about\nit is \"bring it to the bench\". For a managed device, `node_read` asks it over the air for what\nit holds now; `node_set`, `node_set_region`, `node_channel_push` and `node_reboot` are the\nwrites, at `act` or through `propose`. Every write answers `confirmed` true only when the\ndevice's own answer matched; `unconfirmed` with a reason otherwise; a write over LoRa can\ntake a minute and silence is not failure. Region, slot 0 and reboot need `confirm` set to the\ndevice's own id, because afterwards it may be unreachable over the air.\n\n## 7. Hand over the decision\n\nAnything that would change a device, a channel or a region is above the on-air line unless\nyou hold `act`. Use\n`propose` with the exact action and arguments and a rationale in the operator's words, and\nsay what changes if they say yes and what the way back is. A region change before travel needs\ntwo QRs: one for the destination and one for the way home; say so.\n\n## Alerts, and what acknowledging does not mean\n\n`alerts` is what is open. At `act` you can `alert_ack`, and it is worth being exact about what\nthat does: it takes a row off the open list and stops it being raised again while the condition\nstill holds. **It does not fix anything and it does not mean the condition is fine.** When the\ncondition genuinely clears the acknowledgement is forgotten, so a recurrence alerts afresh.\nAcknowledge when the operator has decided they know, not to tidy a list you find untidy, and say\nwhich alerts you acknowledged. An alert that came over a link belongs to the site it came from\nand cannot be acknowledged here.\n\n## Before the kit goes somewhere new\n\nRead `config` for the region. Read the brief for where the kit is going. If they differ, the\nfirst proposal is the region, and nothing else until the operator answers.\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","41ac7e0b96d8f215","skill-safety-audit (MilUX meta-skills)","pass with cautions","1.6.1","2026-09-12, Matt Odell, MilUX Ltd","main","e36ec374e05e01a3701b748f80e27ef7fdab4613","skills\u002Fmesh-operate","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-operate",{"tool":46,"command":47},"bunx","bunx skills add MilUX-Ltd\u002Fmesh-manager --skill mesh-operate",{"tool":49,"command":50},"pnpm","pnpm dlx skills add MilUX-Ltd\u002Fmesh-manager --skill mesh-operate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmesh-operate\u002FSKILL.md",true,[],[55,60,66,72,78,84],{"skillNo":56,"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":57,"categories":58,"keywords":59,"publishedAt":19},"01M7C2W3PHDDSA6HQEQ4FAV2F7","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fsrc\u002Fmesh_manager\u002Fbrief\u002Fskills\u002Fmesh-operate\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"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","mesh-onboard","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":62,"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},"01M7C2VMRR78NEDSBNED686991","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.","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmesh-onboard\u002FSKILL.md",[],[],{"skillNo":85,"name":68,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7C2V23YHY4CC6C7CEMR9ZEM","Diagnose a Meshtastic mesh through Mesh Manager and know which signals to believe. Use before concluding anything is broken, when nodes vanish, when a radio looks alive but says nothing, when a node you do not recognise appears, or when positions are coarse. Names the tools behind each check.","https:\u002F\u002Fgithub.com\u002FMilUX-Ltd\u002Fmesh-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmesh-lessons\u002FSKILL.md",[],[]]