Skip to main content
skill CX Codex

start · nimbalyst — Claude Code skill: what it does and how to install

This skill introduces Nimbalyst Wiki and guides the first steps: create a repository wiki, record decisions, or look up what the team settled on.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add nimbalyst/nimbalyst --skill start -a claude-code
Open on GitHub

What start does

The skill gives a short tour of Nimbalyst Wiki, a local wiki maintained by agents. Run /nimbalyst-wiki:setup to build its initial pages from the repository; use /nimbalyst-wiki:capture to add a session decision to the relevant page. Before working on an area, /nimbalyst-wiki:recall can surface earlier decisions. The start skill itself does not create or edit pages.

You can view and edit the wiki in a browser. Later, /nimbalyst-wiki:team moves a local wiki to Nimbalyst Teams and invites teammates; /nimbalyst-wiki:connect connects a team wiki. A local wiki needs no account. If the repository already has one, the skill points you toward using it instead of setting it up again.

What it helps with

  • build initial wiki pages from a repository
  • record a session decision on the relevant page
  • retrieve earlier decisions before working in an area
  • open the local wiki in a browser
  • move a wiki to Nimbalyst Teams and invite teammates

Example prompts for the agent

  • Explain what Nimbalyst Wiki does and suggest a first step.
  • We decided to keep project conventions in the wiki. Show me how to record that.
  • Find our decision about the API structure and open the wiki in my browser.

How to install start

1Skills CLI (Vercel)

npx skills add nimbalyst/nimbalyst --skill start -a claude-code

2Manually: put the files in place

~/.claude/skills/start/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/start/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about start

How do I install start in Claude Code?

Run npx skills add nimbalyst/nimbalyst --skill start -a claude-code. The skill file is at ~/.claude/skills/start/SKILL.md.

What does the start skill do?

It introduces Nimbalyst Wiki and walks through creating a local wiki, recording decisions, and finding them later. The skill does not write wiki pages itself.

Does a local Nimbalyst Wiki require an account?

No. The local wiki works without an account; Nimbalyst Teams is an optional later step for team use.

Source text

SKILL.md · MIT
---
name: start
description: "Start using Nimbalyst Wiki: show how agents build a local wiki, capture decisions, track typed pages, open the local browser view, and optionally use a team wiki. Use when the user asks what this plugin does, which skills it has, or how to begin."
argument-hint: "[optional goal]"
---

Give a short tour of Nimbalyst Wiki and point at the next step. Do not write any pages in this skill.

Say, in a few lines:

1. Nimbalyst Wiki is a local wiki your agents write for you, so you can think, organize, and set direction.
2. Best first step: `/nimbalyst-wiki:setup`. The agent builds the first wiki from this repository: Home, a writing guide, and starter pages.
3. The habit: at the end of a session, `/nimbalyst-wiki:capture` records what was decided in the page it affects.
4. Before working in an area, `/nimbalyst-wiki:recall` (or asking "what did we decide about X?") answers from the wiki's pages and decisions.
5. Growth paths: typed pages and tables to track things; reading and editing the wiki in the browser (ask "open the wiki in my browser"; the agent calls `openWikiInBrowser`, nothing to install); and optionally connecting a Nimbalyst Team wiki later (`/nimbalyst-wiki:connect`). A local wiki can be moved to Nimbalyst Teams later in one step with `/nimbalyst-wiki:team`, which also invites teammates; they need nothing installed to read it in the browser.

If the user gave a goal, tailor the next step to it. Check whether a local wiki already exists in this repository; if it does, suggest `capture` or asking a question about it instead of `setup`.

Mention the team add-on and its sign-in (the `team` skill installs `nimbalyst-wiki-team`) only if the user chooses the team wiki. The local wiki needs no account. Do not say the install runs onboarding by itself; it does not. The README has the full guide.

© nimbalyst · MIT · nimbalyst/nimbalyst

Similar skills

All skills for Agent setup: memory, context, orchestration →

start by other authors comes first.

start official anthropics Checks connected MCP servers and surveys bio-research tools. Helps researchers get oriented with the plugin before starting a project. CX Codex +1 4,900installs start Donchitos Onboarding guide for Claude Code Game Studios projects. It inspects repository state, sets project stage and rigor, and points to the next workflow step. CX Codex +1 461installs start official Zoom This skill identifies what you need to build or fix with Zoom, then points to the relevant workflow. Use it as the entry point for Zoom API, SDK, OAuth, and integration questions. CX Codex GP ChatGPT ★ 7,604repo stars start TakaGoto Walks a newcomer through picking a language and track, scoring their level, and running a first RAG pipeline in the same session. CX Codex +1 ★ 24repo stars setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs ask-matt Matt Pocock Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug. 766,587installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. 711,230installs writing-plans Jesse Vincent This skill turns requirements for a multi-step task into an implementation plan before code changes begin. It helps when another engineer needs exact files, interfaces, and checks. CX Codex 282,859installs caveman-review JuliusBrussee Turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 411,800installs caveman-compress JuliusBrussee Compresses CLAUDE.md, todo lists, and other prose files into a shorter format while retaining a readable backup. CX Codex +1 411,500installs

From the same set10

feedback-intake Prepare a Nimbalyst bug report or feature request with consent-based evidence gathering, text anonymization, and a draft GitHub Issue. CX Codex +1 ★ 1,979repo stars extension-development A skill for Nimbalyst extension work: build, install and hot-reload extensions from inside the running app through MCP tools. CX Codex +1 ★ 1,979repo stars git-commit This skill prepares a commit proposal in Nimbalyst’s interactive widget. Use it after clicking “Commit with AI” or explicitly requesting a smart commit. CX Codex +1 ★ 1,979repo stars datamodellm Lets the agent draft database schemas in Prisma format for the DataModelLM visual editor. Useful when you want an ERD or a data model before writing code. CX Codex +1 ★ 1,979repo stars update This skill writes and maintains project wiki pages: decisions, open questions, links and citations. Useful when team agreements need to land in a shared page tree. CX Codex +1 ★ 1,979repo stars setup Creates a project wiki with a populated Home page, starter sections and a writing guide. Useful when a team needs documentation it can actually read and navigate. CX Codex +1 ★ 1,979repo stars connect This skill selects a local or team wiki for the session and links a repository to its team project. Use it before wiki work. CX Codex +1 ★ 1,979repo stars capture Writes the decisions made during a session into the wiki pages they affect. Useful when the reasoning matters as much as the code. CX Codex +1 ★ 1,979repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor