DC meshtastic-detection
Receive DETECTION_SENSOR_APP alerts from Meshtastic LoRa devices via USB. When the remote sensor GPIO triggers (preset target detected), store the event and alert the user immediately.
Not recommendedcritical or high security findings · low grade D
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
Dangerous commands
If you install
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
For the author
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 13
-
high Dangerous commands
cmd-persistenceREADME.md:85Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load ~/Library/LaunchAgents/com.openclaw.meshtastic-detection.plist
-
high Dangerous commands
cmd-persistenceREADME.md:88Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl unload ~/Library/LaunchAgents/com.openclaw.meshtastic-detection.plist
Medium and low: 11
-
medium Dangerous commands
cmd-privilegeREADME.md:73Privilege escalation / world-writable permissionssudo cp meshtastic-detection.generated.service /etc/systemd/system/meshtastic-detection.service
-
medium Dangerous commands
cmd-persistenceREADME.md:84Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)cp com.openclaw.meshtastic-detection.plist ~/Library/LaunchAgents/
detector -
medium Dangerous commands
cmd-privilegereferences/SETUP.md:146Privilege escalation / world-writable permissionssudo cp references/meshtastic-detection.service /etc/systemd/system/
-
medium Dangerous commands
cmd-persistencesetup.sh:217Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)echo " launchctl unload ~/Library/LaunchAgents/com.openclaw.meshtastic-detection.plist"
code literal -
low Dangerous commands
cmd-background-processREADME.md:75Starts a background / autostarted processsudo systemctl enable --now meshtastic-detection
-
low Dangerous commands
cmd-background-processREADME.md:97Starts a background / autostarted processnohup ./entrypoint.sh > data/entrypoint.log 2>&1 &
-
low Dangerous commands
cmd-background-processreferences/SETUP.md:164Starts a background / autostarted processsudo systemctl enable meshtastic-detection
-
low Dangerous commands
cmd-persistencesetup.sh:213Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)echo " cp com.openclaw.meshtastic-detection.plist ~/Library/LaunchAgents/"
detectorcode literal -
low Dangerous commands
cmd-persistencesetup.sh:214Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)echo " launchctl load ~/Library/LaunchAgents/com.openclaw.meshtastic-detection.plist"
detectorcode literal -
low Dangerous commands
cmd-privilegesetup.sh:265Privilege escalation / world-writable permissions (string literal in code, not executed)echo " sudo cp meshtastic-detection.generated.service /etc/systemd/system/meshtastic-detection.service"
code literal -
low Dangerous commands
cmd-background-processsetup.sh:267Starts a background / autostarted process (string literal in code, not executed)echo " sudo systemctl enable --now meshtastic-detection"
code literal
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1557 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 184: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.
External checks
ClawHub: suspicious
The skill appears to be a real Meshtastic alert receiver, but it needs review because setup can make privileged system changes and alert instructions may expose sensor details to Feishu unless reconfigured.
LLM: suspicious (high) · VirusTotal: · 29 May 2026