claudetools/.claude/memory/feedback_rmm_search_skill.md at b83057f6e2e5c5e4f254a3cecbcd2ab0b9bd6dec

Files

Mike Swanson 6e1c65877f sync: auto-sync from GURU-5070 at 2026-06-15 11:20:33

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-15 11:20:33

2026-06-15 11:20:56 -07:00

1.2 KiB

Raw Blame History

name, description, metadata

name

description

metadata

feedback-rmm-search-skill

Use the rmm-search skill to find GuruRMM machines, never grep /api/agents by hand

type
feedback

To locate a machine/agent in GuruRMM, use the rmm-search skill (bash .claude/scripts/rmm-search.sh <words> [-c <client>]) — do NOT pull /api/agents and grep client-side.

Why: Hand-grepping bleeds across clients and picks the wrong box — e.g. searching hyperv returns both Valley Wide's and Dataforth's hyperv hosts, and it's easy to act on the wrong one. Mike built the UI Omnibox for this and asked for a CLI equivalent (2026-06-15). rmm-search treats every query word as a required filter across hostname/client/site/OS (so hyperv valleywide can only return Valley Wide's box), is normalized (case/space/hyphen-insensitive) with typo tolerance, and -c <client> hard-scopes (refuses to guess on ambiguous client names).

How to apply: rmm-search.sh hyperv valleywide or ... hyperv -c valleywide to find; --json | jq -r '.[0].id' to get the agent id; then hand hostname/id to the reference_gururmm rmm skill to actually run commands. Online state is from last_seen (<5min), not the unreliable is_connected flag. Engine: rmm-search.sh + rmm-search.py.

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History