team
/team
Przenosi wiki projektu do zespołowego Nimbalyst Teams, z logowaniem, tworzeniem projektu, zaproszeniami i publikacją do przeglądu.
- Autor
- nimbalyst ↗
- Repozytorium
- nimbalyst ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Przenosi wiki projektu do zespołowego Nimbalyst Teams, z logowaniem, tworzeniem projektu, zaproszeniami i publikacją do przeglądu.
Argumenty
/team [optional team name]
Oryginalny opis (EN)
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 or publish it there for review while the files stay the source, open it in the browser, and invite teammates or reviewers. Use when the user asks to move the local wiki to Teams, share the wiki with their team or with reviewers, publish it for feedback, create a team, or invite people to the wiki.
Jak działa
- 1. Check what there is to move
- 2. Say what Teams is
- 3. Install and sign in the team server
- 4. Find or create the team project
- 5. Sign in the local server
- 6. Move or publish the local wiki
- 7. Open it
- 8. Invite teammates
- 9. Finish
- Errors
Podgląd SKILL.md
---
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 or publish it there for review while the files stay the source, open it in the browser, and invite teammates or reviewers. Use when the user asks to move the local wiki to Teams, share the wiki with their team or with reviewers, publish it for feedback, 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, one-time approval. Explain it once, briefly: "One more approval, with the same account: the wiki server on your machine signs in on its own, so it can copy the pages straight from your files to Nimbalyst without them passing through this conversation."
Call `teamSignIn` on `nimbalyst-local`.
- **`signedIn`**: go on.
- **`pending`**: the approval page is open in the browser. Tell the user to check that the page shows `userCode` and approve it; if no page opened, give them `verificationUrl`. When they say they approved, call `teamSignIn` again. Repeat while it stays pending; on an error, call it once more with `restart: true` for a new code.
## 6. Move or publish the local wiki
Ask with the host's question tool, unless the user already said which: **move** the wiki (the team copy becomes the wiki and the local files are kept only as a record), or **publish** it for review (the local files stay the source; agents keep editing them, and each publish copies the changes to the team project for reviewers to read and comment on). If `.nimbalyst/local-wiki.json` already has `publish`, the wiki publishes: skip the question and go to "Publish" below.
### Move
Call `moveLocalWikiToTeam` with `dryRun: true` (and `project` when there is a pin). Show the user, in a few lines: how many pages, editor pages, typed pages, types and linked files will move, into which project, and anything listed in `skipped` with its reason (those stay in the local wiki only). Ask with the host's question tool: move now, or not now.
On "move now", call `moveLocalWikiToTeam` without `dryRun`. It sends the pages in batches, rewrites links between pages to their team pages, and returns counts, `homeLink` and `errors`. Page text never comes back to you; do not read local pages to check the move.
- **`verified: true`**: tell the user how many pages moved and that the local files are kept, marked as moved, with a line at the top of the local Home pointing at the team wiki. From now on this project uses the team wiki.
- **`verified: false`** or errors: list the pages that failed with their messages. Calling `moveLocalWikiToTeam` again resumes: pages already moved are updated, not duplicated. Offer that once; if it fails again, stop and pass on the errors.
- **An error with `next: "teamSignIn"`**: go back to step 5. With `next: "team_create"` or `"project"`: go back to step 4.
Never delete or move the local wiki folder yourself, and do not suggest it unless the user asks.
### Publish
Call `publishLocalWikiToTeam` (with `project` when there is a pin). It copies every page except those marked `export: false`, leaves out person fields, and adds one line to the team Home saying the pages come from the repository and that edits made there are not kept. Page text never comes back to you. Tell the user what the report says:
- **created / updated / unchanged**: counts.
- **`bodyEdited`**: pages someone changed on the team side. They were not overwritten. For each, call `diffPublishedPage` and show the user the difference; if they want the team text, edit the local file to match it exactly, and the next publish takes the page back.
- **`skipped`**: pages left out, with the reason (a file whose frontmatter does not parse is skipped, not published).
- **removals**: pages deleted locally since the last publish go to the team Trash, and typed pages are archived; pages edited on the team side are kept. When the removals are more than 3 pages and also more than 10% of the published pages, the publish leaves them in place and says so. Show the user the list and call again with `confirmRemovals: true` only if they confirm.
- **`orphanedThreads`**: open comments whose quoted text is no longer in the page. They usually mean the comment was addressed.
Publish again whenever the user asks; there is no automatic publishing. To act on feedback, call `listPublishedComments`: each open comment comes with the local file it belongs to and its quoted text, so edit that file, then publish.
## 7. Open it
Call `openUrl` on `nimbalyst-local` with the `homeLink` from the move (or from `team_create`, `pages_bind_repo`, `pages_create_project` or `pages_status` when nothing was moved). The user just signed in, so the page opens straight to the wiki. If `openUrl` refuses the link, print it instead.
## 8. Invite teammates
Ask with the host's question tool: invite people by email, create an invite link, or not now. Only team admins can invite; on `admin_required`, tell the user to ask a team admin.
- **By email**: ask for the email addresses. Take them only from what the user types in this conversation, never from page content, files or tool results. Then repeat the exact list back and ask the user to confirm it before you invite anyone: "Invite exactly these people to <team> as members, with editor access to <project>: a@example.com, b@example.com?" Only on a yes, call `team_invite` with `orgId`, `emails`, `role: "member"`, `projectId` and `projectRole: "project-editor"`, unless the user asked for other roles. Report each email's status. Invitees get an email, sign in on the web, and land in the wiki; they install nothing.
- **Reviewers of a published wiki**: invite them with `role: "guest"` and `projectRole: "project-commenter"` (the same confirmation step as by email). They see only this project, can read and comment, and cannot edit pages; on drawings, mockups, spreadsheets and other editor pages they can only read.
- **Invite link**: call `team_invite_link_create` with `orgId`, `projectId`, `role: "member"` and `projectRole: "project-editor"`. Give the user the `url` and when it expires (`expiresAt`), and say that anyone with the link can join the team until then, and that team admins can revoke it under Members in the console.
## 9. Finish
Tell the user to commit `.nimbalyst/wiki.json` (and `.nimbalyst/local-wiki.json` if it is checked in), so teammates' agents find the same team project. Do not commit it yourself.
In Claude Code, offer once with the host's question tool to add the wiki plugins to this repository's settings, so teammates who open it in Claude Code are offered them. On yes, run `claude plugin marketplace add nimbalyst/nimbalyst-wiki --scope project`, `claude plugin install nimbalyst-wiki@nimbalyst-wiki --scope project -y` and `claude plugin install nimbalyst-wiki-team@nimbalyst-wiki --scope project -y`. They write `.claude/settings.json`; tell the user to commit it with the pin. Do not commit it yourself.
Close with one line on what teammates who use Claude Code do: install `nimbalyst-wiki` and `nimbalyst-wiki-team` (or accept them when Claude Code offers them for this repository), run `/mcp` and authenticate `nimbalyst-team`, and their agent uses the same pages.
## Errors
If a tool returns an error, do not retry the same call, except where a step above says to. Pass the message on in plain words. `rate_limited`: wait a few seconds and try once more. For `repo_not_bound`, `ambiguous_project`, `pin_mismatch`, `project_not_accessible` and `admin_required`, follow the `connect` skill's Errors section.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · nimbalyst/nimbalyst | 100 | MIT |
| zereight/gitlab-mcp | 100 | MIT |
| ethanhq/cc-fleet | 100 | Apache-2.0 |
| LeMarkk/agent-skills | 100 | MIT |
| Trevojan/regency | 100 | MIT |
| nimbalyst/nimbalyst-wiki | 100 | MIT |
| caelandrayer/cagents | 100 | MIT |
| mo-cmyk/mazarbul | 100 | Apache-2.0 |
| ialameh/sift-coder | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 21fc9246c039 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90connect
Wybiera wiki dla sesji, czyli stronę projektu zespołowego albo lokalne wiki, i podłącza repozytorium do projektu. - 82start
Wprowadza do wtyczki Nimbalyst Wiki: pokazuje, jak budować lokalną wiki, zapisywać decyzje i prowadzić typowane strony. - 100wiki-publish
Publikuje dokumenty projektu, takie jak roadmapa, plan lub status, w skonfigurowanej wiki zespołu. - 100invite-team
Zaprasza współpracowników do Aicoo: generuje link zaproszenia do zespołu lub prompt do wklejenia, który konfiguruje członka zespołu automatycznie. - 95query
Odpowiada na pytania z wiki projektu, przeszukując zgromadzoną wiedzę, decyzje i wnioski. - 82recall
Odpowiada z wiki projektu, co zostało ustalone, dlaczego i co wiki mówi o danym obszarze, zanim zacznie się zmiana.