Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

teamem-onboarding | teamem

Skill

teamem-onboarding

Walk a first-time user through Teamem setup — create or join a space, write credentials, verify the bridge resolves. Use when the user has just installed the plugin and has no `~/.teamem/credentials.json` yet, or when `/teamem-setup` is invoked.

$

npx claudepluginhub rubiyh/teamem --plugin teamem

Popularity

Parent stars

1

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/teamem:teamem-onboarding

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

You are guiding a first-time user through Teamem onboarding. The whole flow runs against the bundled setup CLI shipped with the plugin (`${CLAUDE_PLUGIN_ROOT}/lib/setup.js`) — no source-tree dependency.

Supporting Files

SKILL.md

50 lines · ~828 tokens

Similar Skills

karpathy-guidelines

168.3k

Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.

andrej-karpathy-skills

skill-lookup

163.4k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

debugging-and-error-recovery

52.4k

Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.

Stats

LanguageTypeScript

Parent stars1

MaintenanceGood

Last CommitMay 13, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Teamem Onboarding

You are guiding a first-time user through Teamem onboarding. The whole flow runs against the bundled setup CLI shipped with the plugin (${CLAUDE_PLUGIN_ROOT}/lib/setup.js) — no source-tree dependency.

Preconditions to verify

bun is on the user's PATH. If not, link them to https://bun.sh and stop.
~/.teamem/credentials.json does NOT yet exist (or the user explicitly wants to add another space).
${CLAUDE_PLUGIN_ROOT}/lib/setup.js exists. If missing, the plugin install is broken — instruct the user to reinstall via claude plugin install from a Teamem source checkout that ran bun run build:plugin first.

Flow

Path A — first-time, creating a brand-new space

Confirm the user wants to create a new space (vs joining an existing one).
Ask for a space label (human-readable, e.g. "team-alpha", "kernel-rewrite"). It is NOT secret — it appears in the briefing.
Ask for the member name the user wants to be known by inside the space (their principal). The bundled CLI pre-fills the default from git config --global user.name (falling back to $USER); the user can override.
Ask for the server URL (defaults to http://localhost:3000 for local Docker or local Bun; production deployments use a custom HTTPS URL).
Run the bundled setup CLI interactively:
```
bun run "${CLAUDE_PLUGIN_ROOT}/lib/setup.js"
```
Forward all prompts to the user verbatim and pass their answers through. If the CLI explains the coordination default, keep it on auto-skip; negotiator automation is postponed in this plugin build.
After setup completes, the CLI prints a room code the user can share with teammates. Surface this prominently — it expires (default 24h).

Path B — joining an existing space

Ask the user for the room code their teammate gave them.
Ask for the member name they want.
Ask for the server URL their team uses (must match the creator's server).
Run bun run "${CLAUDE_PLUGIN_ROOT}/lib/setup.js" and paste the room code at the prompt.

After successful setup

Tell the user the credentials live at ~/.teamem/credentials.json (mode 0600).
Tell them to run /teamem-on to activate the plugin for this session, optionally with --persist for project-wide auto-on.
Tell them the first thing the plugin will do on activation is fetch a briefing — no claims yet.

Common failure modes

server unreachable: ask the user to verify the server URL with curl <url>/health. If they're running local-docker, suggest docker compose up -d from a Teamem source checkout.
invalid_code / code_expired: room code is wrong or older than 24h. Ask the creator to run /teamem-space rotate-code and resend.
bridge_bundle_missing: the plugin's lib/setup.js or lib/bridge.js is absent. Reinstall via claude plugin install from a checkout that ran bun run build:plugin.
setup mid-flight failure: tell the user to delete ~/.teamem/credentials.json and retry.