Teams and private libraries
Share kits inside your team or company without listing them publicly, with roles for who manages what.
Some kits are only useful inside one group: your company's report format, your team's way of handling support tickets, a client's checklist. A team on SlashClone, called an organization in Settings, gives those kits a home that only its members can see.
What a team gets
- Its own page and handle, like
@acme. Anyone can see the team's name and any public kits it shares. - A private library. A private kit owned by the team is shared with every member and nobody else. On the team's page it carries an Org only label. These kits never appear in search, for anyone.
- Roles, so a few people manage the team and everyone else just uses and adds kits.
- A member list, which only members see.
Create a team
- Go to Settings, Organizations.
- Under New organization, enter a Handle (the short name in the team's address) and a Name.
- Click Create organization. You are its first owner.
Invite people
Each person you invite needs their own SlashClone account first.
- On the team's page, click Org settings. You can also get there from Settings, Organizations.
- Open Members and invites. Under Invite a builder, enter their handle, choose a Role, and click Send invitation.
- They get a notice and click Accept or Decline, on the team's page or in their own Settings, Organizations.
Admins can revoke an invitation that is still waiting. A member can leave with Leave on the team's page, and loses access to its private kits.
Roles
- Owner: handles billing and decides who else is an owner. A team always keeps at least one.
- Admin: invites and removes members, changes roles, and manages the team's settings.
- Member: uses the library and adds kits to it.
Only owners can make someone an owner.
Add a kit to the library
Any member can add a kit. What makes it a team kit is its owner. It belongs to the team, not to you. When a kit names the team as its owner, the share page says Shared under @acme. Choose Private before you share it. In a team's library, private means every member and nobody else.
To check, open the team's page. The kit shows under Library with the Org only label.
You can do the same from Claude. Ask it to share the skill to your team, for example "Share this skill to @acme." Claude saves it under the team instead of your profile, and you choose who sees it before it goes out. Only members can add to a team, so check you have joined first. A new version of a team kit goes back to the team on its own.
Team kits in Claude
Team kits stay out of search, so ask for them by name. Connect SlashClone to Claude with your own account, then say something like "Install @acme/weekly-report." Because you are a member, Claude can open it, show you what it does and what it may touch, and set it up the same way as any other kit (Find and use your first kit). The team's page lists every kit in its library. If your team asks members to sign in with its single sign-on, do that first, or its private kits stay hidden.
Free, and the Team plan
Creating a team is free. On the free plan, the team's private kits count toward the free limit on private kits.
The Team plan adds tools for companies: Required kits (kits every member should have), an Install policy (limits on which public kits members install), Single sign-on, and an Audit log. It is billed per member. Seats follow the member list as people join and leave, and invitations still waiting do not count. Only owners can move a team to it, from Org settings, Team billing. Pricing shows the current price.
Who it is for
A team fits any group that works from the same kits: a company, one team inside it, or a few people building together. If a kit is only for you, keep it private on your own account instead.
