Repository navigation
Add three new tools and a community tool folder - #1
Merged
Merged
Conversation
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>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 intools.jsonandBUILTIN_TOOLS. Each has its own test file.Bug fixed during testing: Switch Additional CLI loaded its sites through
ctx.listSites(), which trims each site to{id, name}. That droppednetworktemplate_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.jschecks each contribution. It must pass the installer'scheckToolSource, load throughvalidateTool, 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.CONTRIBUTING.md, an MITLICENSE, a PR checklist template and a tool-request issue template..github/workflows/test.ymlrunsnpm test(Node 20, no dependencies) on every PR and every push to main.Verification
npm test: 220/220 pass (198 before this PR).npm run scan: all 12 tools validate.fetch()directly and has no README row fails both community tests with clear messages.community/folder and does contain the three new tools.Screenshots of the new tools are not included.
🤖 Generated with Claude Code