Move the wiki to Nimbalyst Teams

Walk the user through these steps in order. Each step says what to call and what to tell the user. The connect skill covers choosing a wiki and the repo and project arguments; this skill uses them the same way.

If the desktop app's wiki tools are available (mcp__nimbalyst-trackers__*), stop: the Nimbalyst app moves pages to a team itself (Move to Team in the page menu). Say so and do not use this plugin's tools.

1. Check what there is to move

Call listPages on nimbalyst-local.

• Pages come back: there is a local wiki to move. Note roughly how many pages it has.
• "No local wiki": there is nothing to move. Say so, and continue from step 2 only if the user still wants a team wiki; skip steps 5 and 6.
• If .nimbalyst/local-wiki.json already has migratedTo, the wiki was already moved. Say so, and do steps 3 and 4 with project set to the orgId and projectId it names (pages_status returns its homeLink), then skip to step 7 (open it) and step 8 (invites).

2. Say what Teams is

In two sentences, no more: "Nimbalyst Teams keeps the wiki on the Nimbalyst server, shared live with your team, with history and comments. Teammates read and edit it in their browser with nothing to install, and their agents use the same pages."

3. Install and sign in the team server

The nimbalyst-team server comes in a small add-on plugin, nimbalyst-wiki-team, so people who only use a local wiki are never asked to sign in. If its tools (pages_status and the rest) are available, skip to "Sign in" below.

Install the add-on

Check whether it is installed: in Claude Code run claude plugin list, in Codex codex plugin list, and look for nimbalyst-wiki-team. If it is installed, skip to "Sign in".