Team quickstart: from new org to a team skill

Set up a team on app.openworklabs.com, publish your first skill, and trigger it from the desktop app — in about 15 minutes. By the end of this walkthrough you will have:

1. Created an organization on OpenWork Cloud.
2. Invited a few teammates and organized them into teams.
3. Created a plugin with a simple test skill in Plugin Directory and added it to a Collection.
4. Granted the Collection to the relevant team.
5. Signed in to the org from the OpenWork desktop app and triggered the skill with a plain-language prompt.

---

​

1. Create your organization

Head to app.openworklabs.com. Enter your work email and press Next — OpenWork routes you to the right sign-in step automatically. New emails get the Create your account. step. Pick a name and password, then Sign up. Right after sign-up, OpenWork asks you to name your team. This creates your organization — you can rename it later, and no credit card is required. You land in the admin dashboard with a short setup checklist. You can follow it now or come back later — this tutorial covers the important parts.

​

2. Invite teammates and create teams

Open Members in the sidebar. Click Add member, enter your teammate’s email, pick a role (Member or Admin), and hit Send invite. Repeat for a few teammates. Invited people show up as Pending until they accept. From the row menu (⋯) you can Copy invite link, Resend invite, or Cancel invite. Your teammate opens the invite link, sets a password, and joins with one click: Now organize people into teams. Switch to the Teams tab, click Create Team, name it (for example Sales), and tap the members who belong in it. Teams show up with their members at a glance:

​

3. Create a plugin with a test skill

Skills are step-by-step instructions the agent loads when a task matches — think of them as runbooks your whole team can share. A skill lives inside a plugin, and a Collection groups one or more plugins for assignment. First open Collections, click New collection, and create one for your team — for example Sales Enablement. Next open Plugin Directory → Create plugin. Fill in the plugin name and description, then click + Skill. Write the skill like a great runbook:

• Name — e.g. Prep a sales call
• Description — when should the agent use this? e.g. “Use when someone asks to prepare for a sales call or customer meeting.”
• Instructions — plain markdown with the steps you want the agent to follow.

In the Share section, choose the Sales Enablement Collection. If only selected teams should receive it, leave Share with everyone in the organization off. Click Create plugin. The creator keeps access automatically.

​

4. Give teams access to the Collection

Open Collections → Sales Enablement. Under Who can access this, add the Sales team. You can instead grant the Collection to everyone in the organization or to individual members. That’s the whole admin loop: skill inside a plugin → Collection → team or member. Anyone added to the team later inherits access to the Collection.

​

5. Trigger the skill from the desktop app

Now switch to the OpenWork desktop app. On the welcome screen, click Joining a team? Sign in and sign in with the same account. Pick your organization: You can confirm the connection any time under Settings → Account: Open Settings → Library and filter to Skills. The skill assigned through Sales Enablement appears there automatically; click Refresh if the admin changed access moments ago. Now just ask for the thing the skill knows how to do. Type a prompt that matches the skill’s description and hit Run task:

Prep me for tomorrow’s sales call with Northwind Traders. 30 minutes with their operations lead, goal is a paid pilot.

The agent picks up the skill and follows your runbook — research, a timed agenda, discovery questions, objection handling, and a clear next step, saved as a doc in your workspace:

​

What’s next

• Add more skills to the plugin as your team’s playbooks grow — everyone gets updates automatically.
• Import existing plugins from GitHub (Plugin Directory → Create plugin → Import from GitHub), including Anthropic-compatible plugin repositories.
• Wire up Sources to keep Collections in sync with a repository.
• Read Collections when you need several plugins, reusable audiences, or more complex assignments.