set-up-openwork-team

Set up OpenWork for a team - sign up for OpenWork Cloud, create the organization, invite teammates, share models through the AI Gateway, and share a skill. Use when a team or company wants OpenWork with shared skills, models, or policies.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Set up OpenWork for a team

OpenWork Cloud is the team control plane: members, shared models (AI Gateway), shared skills and plugins, and the MCP Gateway. The first 5 seats are free; then $10 per seat per month. Pricing: https://openworklabs.com/pricing

The human creates the account. Don't invent passwords or create accounts for the user without asking.

Recommended: dashboard (about 15 minutes)

Sign up: https://app.openworklabs.com?mode=sign-up. Right after sign-up, the user names their team; that creates the organization. No credit card.
Invite teammates: Members > Add member, enter an email, pick a role (usually Member), Send invite. Group people under Teams > Create Team.
Share models: AI Gateway > AI Providers > Add provider, pick a provider, paste the org key, and choose who can use it. Members never handle keys.
Share a skill: create a Collection (Collections > New collection), then Plugin Directory > Create plugin > + Skill. Write a name, a "use when..." description, and markdown instructions. Share it to the Collection and grant the Collection to a team.
Everyone installs the desktop app (skill: https://openworklabs.com/.well-known/agent-skills/install-openwork/SKILL.md) and clicks Joining a team? Sign in. Shared skills appear under Settings > Library.

Walkthrough with screenshots: https://openworklabs.com/docs/cloud/team-quickstart

Headless: let the agent set it up

When the user wants the agent to do the setup from a terminal, follow https://openworklabs.com/start.md. It installs the openwork-bootstrap CLI (needs Node.js 20+; it is not on npm) and creates a provisional workspace with a first skill. The human claims ownership later in the browser, so no password is created by the agent.

curl -fsSLo /tmp/openwork-install.sh https://openworklabs.com/install.sh
less /tmp/openwork-install.sh   # inspect before running
sh /tmp/openwork-install.sh
openwork-bootstrap doctor --json

Then run openwork-bootstrap cloud bootstrap-workspace exactly as start.md describes. Teammate emails passed with --teammate-emails are invited once a human claims the workspace.

To keep building in that workspace before anyone claims it (adding skills and connections through the MCP gateway), or to sign the CLI in as an existing user without a password, follow https://openworklabs.com/auth.md.

Then: bring OpenWork into the team's agents

Each member can connect their coding agent to the organization with the connect-openwork-mcp skill: https://openworklabs.com/.well-known/agent-skills/connect-openwork-mcp/SKILL.md

Needs SSO, SCIM, audit, or self-hosting?

Send the user to https://openworklabs.com/enterprise.

Repository: different-ai/openwork
Path: ee/apps/landing/public/.well-known/agent-skills/set-up-openwork-team/SKILL.md
Commit: 417244c

Last updated: 2 days ago
First committed: 4 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.