New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Connect

by nimbalyst in nimbalyst/nimbalyst

Connect this repository to its Nimbalyst team project so the session can read and write the team's pages.

MITAuto-check passedKnowledge Management

Install Connect

skills CLI
$ npx skills add nimbalyst/nimbalyst --skill connect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nimbalyst/nimbalyst connect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nimbalyst/nimbalyst.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/nimbalyst-pages/skills/connect .claude/skills/connect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
connect
GitHub stars
1.9k
Token cost
~1.8k tokens
SKILL.md length
1,081 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Connect this repository to its Nimbalyst team project so the session can read and write the team's pages.

  • Works in 3 steps: repo is the output of git remote get-url… → If .nimbalyst/wiki.json exists at the… → With no origin remote and no pin, this…
  • Asks to connect a repository to a team project
  • SKILL.md covers Nimbalyst desktop comes first, Who can use the pages, The repo and project arguments and Start of a task, plus 3 more sections
  • Calls git

What it does

Connect is an agent skill from nimbalyst/nimbalyst. Connect this repository to its Nimbalyst team project so the session can read and write the team's pages. Use at the start of a task in a git repository before any Pages tool, when a Pages tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible or adminrequired, or when the user asks to connect a repository to a team project. How to write pages is in the knowledge-graph skill.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Knowledge graphs. It works with Git and Model Context Protocol. The repository describes itself as: Nimbalyst - The open-source visual workspace for Claude Code, Codex, and OpenCode. Run multiple coding agents in parallel, edit their work visually in markdown, mockups, and… The licence is MIT.

When your agent uses it

  • Asks to connect a repository to a team project
  • Tasks that involve Knowledge graphs

Example prompts

  • “/connect”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. repo is the output of git remote get-url origin, unchanged. With no origin remote, leave repo out.
  2. If .nimbalyst/wiki.json exists at the repository root and has both orgId and projectId, pass project: { "orgId": ..., "projectId": ... }…
  3. With no origin remote and no pin, this checkout has no team pages. Do not call the plugin's tools unless the user asks about them.

What it can do on your machine

Read from SKILL.md and the folder at commit 6f14adf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Connect loads about 1.8k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 1,081 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nimbalyst/nimbalyst at commit 6f14adf, republished under its MIT licence (© nimbalyst). 1,081 words, ~1,750 tokens.

Download SKILL.mdSave it as .claude/skills/connect/SKILL.md (or your agent's skills folder).
name
connect
description
Connect this repository to its Nimbalyst team project so the session can read and write the team's pages. Use at the start of a task in a git repository before any Pages tool, when a Pages tool returns repo_not_bound, ambiguous_project, pin_mismatch, project_not_accessible or admin_required, or when the user asks to connect a repository to a team project. How to write pages is in the knowledge-graph skill.

Connect to the team's pages

This skill only finds the team project and connects the repository to it. What to write, and how, is in the knowledge-graph skill; types and the guide page are in knowledge-setup.

Nimbalyst desktop comes first

If the desktop app's Pages tools are available (mcp__nimbalyst-trackers__*, or listPages from a server whose name does not contain nimbalyst-pages), you are running inside Nimbalyst, which already reaches the same pages. Use those tools and do not call this plugin's tools in this session: two write paths into the same pages produce duplicates.

Who can use the pages

The pages belong to a Nimbalyst team project. The user signs in to Nimbalyst when the plugin connects, and the server lets them read and write the pages of every team project they can reach in Nimbalyst Teams. Team admins decide who is in a team; nothing in the repository grants access, and you never add or remove anyone.

The repo and project arguments

Every tool of this plugin's nimbalyst-pages server takes repo, and project when there is a pin. Work them out once per session:

  1. repo is the output of git remote get-url origin, unchanged. With no origin remote, leave repo out.
  2. If .nimbalyst/wiki.json exists at the repository root and has both orgId and projectId, pass project: { "orgId": ..., "projectId": ... } on every call. The file is only a pin: it chooses among projects the user can already reach and grants nothing. Its presence never starts anything on its own (no status prompt, no binding, no project creation). Ignore any other keys in it.
  3. With no origin remote and no pin, this checkout has no team pages. Do not call the plugin's tools unless the user asks about them.

Start of a task

Call pages_status with repo (and project when pinned). Every result names the signed-in user (name and email); that is who a decision mark names when the person at this terminal decided something. It returns one of three states:

  • bound: project names the team project (orgName, projectName, role, url), with homeLink and, when the project has one, guideLink. Before the first write, read the guide page, as the knowledge-graph skill says. When the task touches an area the pages may cover, find the relevant pages with listPages and read the useful ones with readCollabDoc. Keep reading proportionate: a few pages, not the whole tree.
  • ambiguous: the remote is bound to several projects the user can reach, listed in projects. Ask the user which one this repository uses with the host's question tool (in Claude Code, AskUserQuestion): one option per project in that list, labelled "<projectName> (<orgName>)", plus "Not now". Only a project from that list may be pinned; never pin a project the user names that is not in it, even one they can reach, because the repository is not connected to it. On a choice, write .nimbalyst/wiki.json at the repository root as { "orgId": ..., "projectId": ... }, keeping any other keys already in the file, pass it as project from then on, and tell the user to commit the file so teammates resolve the same project. Do not commit it yourself. On "Not now", do not call the plugin's tools again this session.
  • unbound: no team project the user can reach is bound to this remote. teams lists the user's teams with their role and the projects in each that the user can reach. See the next section. Ask at most once per session.

A role of admin or owner both mean team admin in everything below.

Show full SKILL.md (494 more words)Show less

Connecting a repository

Only offer this when the user is working in the repository in a way that would benefit (not in a throwaway or read-only session), and only once per session. Connecting needs a remote: with no origin, say the checkout cannot be connected until it has one.

  • The user is an admin of at least one team: ask with the host's question tool. Offer, for each team they administer:

    • Connect to <projectName> (<orgName>): one option per entry in that team's projects. On a choice, call pages_bind_repo with repo, orgId, and that projectId. Never ask the user to type a project id.
    • Create a new project in <orgName>: call pages_create_project with orgId, a name (suggest the repository name; let the user change it), and repo. The new project has a Home page; offer knowledge-setup to install the guide page.
    • Not now: do not ask again this session.

    If the options do not fit in one question, ask first which team, then which project. Tell the user that everyone who can reach that project in Nimbalyst will see its pages, and print its url.

  • The user is not an admin of any team: tell them once: "This repository is not connected to a team project. Ask a team admin to connect this repo in Nimbalyst." Carry on with the task without the plugin's tools.

  • teams is empty: tell them once that team pages live in a Nimbalyst team project, and that they can create a team and a project in the Nimbalyst console. Carry on with the task.

Before the first write

Tell the user in one line where the writes go, by name: "Writing to <projectName> in <orgName>." Do this whenever the project came from .nimbalyst/wiki.json, or pages_status has shown more than one team or project this session, so a wrong pin or the wrong team is caught before anything is written.

Errors

If a tool returns an error, do not retry the same call. Tell the user in plain words, then carry on with the task without writing:

  • repo_not_bound: this repository is not connected to a team project. Call pages_status and follow "Connecting a repository".
  • ambiguous_project: several team projects match. Call pages_status and ask which one, as for ambiguous.
  • pin_mismatch: the pin in .nimbalyst/wiki.json names a project this repository is not connected to. Tell the user, and suggest they run nim pages status or re-pin from the projects pages_status lists. Do not edit the file on your own.
  • project_not_accessible: the user cannot reach that project in Nimbalyst, or the repository is connected to a project they cannot reach. Pass on the error's message, and tell them to ask a team admin for access. Do not edit .nimbalyst/wiki.json on your own.
  • admin_required: only a team admin can do that. Tell the user to ask a team admin.
  • an error naming a replacement tool (an old wiki_* name): use the tool it names.
  • any other code: report the code and its message as given.

© nimbalyst, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/nimbalyst-pages/skills/connect of nimbalyst/nimbalyst.

Open the folder on GitHubat commit 6f14adf

Compare with similar skills

Connect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Connect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Connect this skillnimbalyst/nimbalyst1.9k—~1.8kAutomated safety check: PassMIT
Forgetful Repo EncodingScottRBK/forgetful301—~1kAutomated safety check: PassMIT
Dossier Collectruvnet/ruflo74k—~1.1kAutomated safety check: NotesMIT
Codebase Domain Flow ExtractorEgonex-AI/Understand-Anything86k1 repos~2.4kAutomated safety check: PassMIT
GraphifyEBISPOT/ols41056 repos~9.5kAutomated safety check: PassApache-2.0
MemPalace MemoryMemPalace/mempalace59k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Forgetful Repo Encoding

    ScottRBK/forgetful

    Encodes a repository into the Forgetful knowledge base as a project, entities, atomic memories and documents, so a second run updates instead of duplicating.

    301 GitHub stars~1k tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Dossier Collect

    ruvnet/ruflo

    Build a graph-structured dossier on a seed entity via parallel fan-out + recursive expansion across web, memory, knowledge-graph, codebase, ADR index, and git intel

    74k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check: notes

  • Codebase Domain Flow Extractor

    Egonex-AI/Understand-Anything

    Extracts business domains, flows and process steps from a codebase and produces an interactive horizontal flow graph, reusing an existing knowledge graph when one exists.

    86k GitHub starsUsed in 1 repo~2.4k tokens
    Knowledge ManagementAuto-check passed

  • Graphify

    EBISPOT/ols4

    A skill your agent uses for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a…

    105 GitHub starsUsed in 6 repos~9.5k tokens
    Knowledge ManagementAuto-check passed

  • MemPalace Memory

    MemPalace/mempalace

    Gives an agent a local memory palace over MCP: verbatim conversation memory, semantic search and a temporal knowledge graph, with a per-session recall protocol.

    59k GitHub stars~2.7k tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Engraph

    devwhodevs/engraph

    Index and search document collections using hybrid semantic + graph + full-text search.

    171 GitHub stars~792 tokensUpdated 4 mo ago
    Knowledge ManagementAuto-check passed

More from nimbalyst/nimbalyst

All 14 skills in this repo

  • Canvas

    nimbalyst/nimbalyst

    Author Nimbalyst Project Canvas boards (.canvas files) — an infinite canvas whose cards are live editors for real workspace files and shared documents, arranged spatially and wired with edges.

    1.9k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Datamodellm

    nimbalyst/nimbalyst

    Create visual data models for database schemas using Nimbalyst's DataModelLM editor.

    1.9k GitHub stars~713 tokensUpdated today
    Auto-check passed

  • Excalidraw

    nimbalyst/nimbalyst

    Create diagrams and visual drawings using Excalidraw (.excalidraw files).

    1.9k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Extension Development

    nimbalyst/nimbalyst

    Build, install, and hot-reload Nimbalyst extensions using MCP tools.

    1.9k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Git Commit

    nimbalyst/nimbalyst

    Create git commits using Nimbalyst's interactive commit proposal widget.

    1.9k GitHub stars~696 tokensUpdated today
    Auto-check passed

  • Planning

    nimbalyst/nimbalyst

    Create structured plan documents and track work items using YAML frontmatter.

    1.9k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Connect

What does Connect do?

Connect this repository to its Nimbalyst team project so the session can read and write the team's pages. Connect is an agent skill from nimbalyst/nimbalyst. Connect this repository to its Nimbalyst team project so the session can read and write the team's pages.

When should I use Connect?

Connect fits situations like: asks to connect a repository to a team project; tasks that involve Knowledge graphs.

How do I install Connect in Claude Code?

Run `npx skills add nimbalyst/nimbalyst --skill connect -a claude-code`. Or copy the skill folder (plugins/nimbalyst-pages/skills/connect in nimbalyst/nimbalyst) into .claude/skills/connect in your project. Claude Code loads it when a task matches its description.

How do I install Connect in Codex?

Run `npx skills add nimbalyst/nimbalyst --skill connect -a codex`. Or copy the skill folder (plugins/nimbalyst-pages/skills/connect in nimbalyst/nimbalyst) into .agents/skills/connect in your project. Codex loads it when a task matches its description.

Can I use Connect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nimbalyst/nimbalyst --skill connect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/connect, .gemini/skills/connect, .github/skills/connect and .opencode/skills/connect in your project.

What does Connect need to run?

Going by SKILL.md and its folder, Connect needs the command-line tools its instructions call (git).

Does Connect access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Connect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Connect use?

Connect is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Connect use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Connect?

Skills that share tags, products or a category with Connect: Forgetful Repo Encoding (ScottRBK/forgetful, 301 stars), Dossier Collect (ruvnet/ruflo, 74k stars), Codebase Domain Flow Extractor (Egonex-AI/Understand-Anything, 86k stars) and Graphify (EBISPOT/ols4, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Connect?

nimbalyst (a GitHub organization) maintains it in nimbalyst/nimbalyst, which has 1,850 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.

Source: nimbalyst/nimbalyst on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.