/team

name: team
description: Put this project's wiki on Nimbalyst Teams: sign in, create or choose the team project, move the local wiki into it in one step, open it in the browser, and invite teammates. Use when the user asks to move the local wiki to Teams, share the wiki with their team, create a team, or invite people to the wiki.
argument-hint: "[optional team name]"

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".

Otherwise ask once with the host's question tool: "The team wiki needs the nimbalyst-wiki-team add-on, which adds the Nimbalyst sign-in. Install it now?" with "Install" and "Not now". On "Not now", stop here and carry on with the local wiki.

On "Install", run these in the terminal yourself, in order:

• **Claude Code**: `claude plugin marketplace list`. If no marketplace is named `nimbalyst-wiki`, run `claude plugin marketplace add nimbalyst/nimbalyst-wiki`. Then `claude plugin install nimbalyst-wiki-team@nimbalyst-wiki -y`.
• **Codex**: `codex plugin marketplace list`. If no marketplace is named `nimbalyst-wiki`, run `codex plugin marketplace add nimbalyst/nimbalyst-wiki`. Then `codex plugin add nimbalyst-wiki-team@nimbalyst-wiki`.

If a command fails, show its output and stop. A session only loads plugins when it starts, so tell the user exactly, then wait:

• Claude Code: "Installed. Type `/exit`, then run `claude --continue` in this folder to come back to this conversation with the team server loaded. Then run `/mcp`, choose `nimbalyst-team`, pick Authenticate, and tell me when it says you are connected."
• Codex: "Installed. Run `codex mcp login nimbalyst-team` in a terminal and sign in, then start a new Codex session here and ask me to continue moving the wiki to Teams."

Sign in

The `nimbalyst-team` server needs the user's Nimbalyst sign-in, and only the user can start it. If the add-on is installed but its tools are not available, or a call returns an authentication error, tell the user exactly:

"Run `/mcp`, choose `nimbalyst-team`, and pick Authenticate. A browser page opens: sign in or create your Nimbalyst account there and approve. Tell me when it says you are connected."

In Codex the command is `codex mcp login nimbalyst-team`, run in a terminal.

Wait for the user. Do not try to sign in some other way, and do not continue until the team tools work.

4. Find or create the team project

Call `pages_status` with `repo` (the output of `git remote get-url origin`, left out when there is no `origin`) and `project` when `.nimbalyst/wiki.json` pins one.

• **`bound`**: the repository already has a team project. Tell the user its name and team, and go to step 5.
• **`ambiguous`**: ask which project, pin it and continue, as the `connect` skill says for `ambiguous`.
• **`unbound` with `teams` empty**: the user has no team yet. Propose a team name: the argument the user gave, else the owner of the git remote (`acme` in `github.com/acme/web`), else the repository name. Ask with the host's question tool, the proposal as the first option and room to type another. Then call `team_create` with `name` and `repo` (leave `repo` out with no `origin`). It creates the team, its first project and that project's Home page, and connects the repository; the result has `orgId`, `projectId` and `homeLink`. If it says the user has created too many teams today, pass that on and stop.
• **`unbound` with teams**: for the teams where the user's `role` is `admin` or `owner`, offer with the host's question tool: connect to one of that team's existing projects (`pages_bind_repo` with `repo`, `orgId`, `projectId`), create a new project in that team (`pages_create_project` with `orgId`, a `name` defaulting to the repository name, and `repo`), or create a new team (`team_create` as above). If the user administers no team, offer two choices: ask a team admin to connect this repository in Nimbalyst (then stop here), or create their own team with `team_create`.

Once there is a project, write `.nimbalyst/wiki.json` at the repository root as `{ "orgId": ..., "projectId": ... }`, keeping any other keys already in the file. With no `origin` remote this pin is the only way the project is found again, so never skip it.

5. Sign in the local server

Moving the pages needs a second,