Nozbe Teams

Nozbe Teams integration. Manage Users, Organizations. Use when the user wants to interact with Nozbe Teams data.

Security Scan

The skill's requirements and runtime instructions match its stated purpose: it instructs the agent and user to use the Membrane CLI to connect to Nozbe Teams and does not ask for unrelated credentials or system access.

Purpose & Capability

Name/description (Nozbe Teams integration) align with the instructions: all actions are performed via the Membrane CLI and relate to listing/creating/running actions and managing connections.

Instruction Scope

SKILL.md sticks to using the Membrane CLI for authentication, connection management, action discovery, creation, and execution. It does not instruct reading unrelated files, accessing unrelated env vars, or exfiltrating data to unexpected endpoints.

Install Mechanism

The skill instructs installing @membranehq/cli via npm (global install or npx usage). This is expected for a CLI-driven integration but still means executing third-party code from the npm registry — a moderate operational risk. The skill itself includes no install spec in metadata and has no embedded code.

Credentials

No environment variables, config paths, or credentials are requested by the skill. Authentication is delegated to Membrane's login flow; the SKILL.md explicitly advises against asking users for API keys or tokens.

Persistence & Privilege

The skill does not request persistent/always-on privileges, does not modify other skills, and does not claim elevated system access.

Assessment

This instruction-only skill is coherent: it directs you to use the official Membrane CLI to connect to Nozbe Teams and does not ask for unrelated secrets. Before installing or running it, consider: 1) review the @membranehq/cli package and its source (GitHub) to confirm you trust it before running a global npm install; 2) be careful when following the login flow — it may produce a short-lived authorization code you will paste or enter; do not share that code publicly or paste it into untrusted chat/history; 3) if you cannot or do not want to install npm packages, the skill suggests npx which runs the package without a permanent global install; and 4) confirm your organization's policy on installing third-party CLIs. If any of these are a concern, decline or audit the Membrane CLI first.

Nozbe Teams is a project management and team collaboration app. It's used by small to medium-sized teams to organize tasks, communicate effectively, and manage projects.

Official docs: https://help.nozbe.com/

Nozbe Teams Overview

• Task
  • Comment
• Team
• Project
• User
• Context
• Category

Use action names and parameters as needed.

Working with Nozbe Teams

This skill uses the Membrane CLI to interact with Nozbe Teams. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run membrane from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add --json to any command for machine-readable JSON output.

Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Nozbe Teams

Use connection connect to create a new connection:

membrane connect --connectorKey nozbe-teams

The user completes authentication in the browser. The output contains the new connection id.

Listing existing connections

membrane connection list --json

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

Use npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json to discover available actions.

Creating an action (if none exists)

If no suitable action exists, describe what you want — Membrane will build it automatically:

membrane action create "DESCRIPTION" --connectionId=CONNECTION_ID --json

The action starts in BUILDING state. Poll until it's ready:

membrane action get <id> --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

• READY — action is fully built. Proceed to running it.
• CONFIGURATION_ERROR or SETUP_FAILED — something went wrong. Check the error field for details.

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Best practices

• Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
• Discover before you build — run membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
• Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.