Skip to content

Add three new tools and a community tool folder - #1

Merged
InterconnectedSystems merged 2 commits into
mainfrom
community-tools
Oct 9, 2026
Merged

InterconnectedSystems merged 2 commits into
mainfrom
community-tools

Conversation

@InterconnectedSystems

Copy link
Copy Markdown
Owner

Three new built-in tools

All three are added as written (the source stays at the repo root, with an identical copy in mist-toolbox/tools/) and registered in tools.json and BUILTIN_TOOLS. Each has its own test file.

Tool Level What it does
Client Wi-Fi PHY Inspector Site · Client Grades one client's RSSI, SNR, noise floor, PHY rate against its ceiling, retries, channel load, non-Wi-Fi interference and overlapping AP radios, as a dashboard plus an .xlsx
Switch PSU Status Site · Org Shows PSU health per switch and per VC member, flagging failed supplies and switches that have lost redundancy
Switch Additional CLI Site · Org Collects the additional CLI at template, switch-rule, site and device level, side by side, with a de-duplicated command list

Bug fixed during testing: Switch Additional CLI loaded its sites through ctx.listSites(), which trims each site to {id, name}. That dropped networktemplate_id, so the template-level CLI was never reported. The tool now reads the full site records.

Community tool folder

  • mist-toolbox/community/ holds user-contributed tools. They are installed with Manage tools → Install, are not built in, and are left out of the release ZIP (build-release.sh).
  • tests/community.test.js checks each contribution. It must pass the installer's checkToolSource, load through validateTool, have a filename that matches its id and an id not used by any other tool, and appear in the community README. The existing policy and imports tests cover the folder too.
  • Adds CONTRIBUTING.md, an MIT LICENSE, a PR checklist template and a tool-request issue template.
  • .github/workflows/test.yml runs npm test (Node 20, no dependencies) on every PR and every push to main.
  • The README and ADDING_TOOLS link to all of it.

Verification

  • npm test: 220/220 pass (198 before this PR).
  • npm run scan: all 12 tools validate.
  • Negative check: a community tool that calls fetch() directly and has no README row fails both community tests with clear messages.
  • The release ZIP has no community/ folder and does contain the three new tools.

Screenshots of the new tools are not included.

🤖 Generated with Claude Code

InterconnectedSystems and others added 2 commits October 9, 2026 18:35
Three new built-in tools, added as written (source kept at the repo root,
identical copy in mist-toolbox/tools/), registered in tools.json and
BUILTIN_TOOLS, with tests for each.

Switch Additional CLI read its sites through ctx.listSites(), which trims
each site to {id, name}, so networktemplate_id was always missing and the
template-level CLI was never reported. It now reads the full site records.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
mist-toolbox/community/ holds user-contributed tools. They are installed
with Manage tools -> Install, not built in, and are left out of the
release ZIP. tests/community.test.js holds each one to the installer's
checks, validateTool, a filename that matches its id, a unique id and a
README listing. A GitHub Actions workflow runs npm test on every push to
main and every pull request.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@InterconnectedSystems
InterconnectedSystems merged commit 8ca62dc into main Oct 9, 2026
1 check passed
@InterconnectedSystems
InterconnectedSystems deleted the community-tools branch October 9, 2026 18:47
@InterconnectedSystems InterconnectedSystems mentioned this pull request Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant