Setup team

Skill arclabshq/arc-labs-studio-team/skills/setup-team

Introduces the Studio Team, explains its 15 skills, and helps users name or rename the eight roles. Use on first run, during onboarding, or whenever the user asks to configure the team roster.From its SKILL.md

Install

npx -y skills add arclabshq/arc-labs-studio-team --skill setup-team

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 376 tokens by cl100k_base, as published. Nobody here has run it

Set Up Team

Welcome the user with this exact substance, in natural language:

You have 15 skills here: eight roles, one thinking mode, and six workflows. Before we begin, what would you like to call each new hire?

Name the roles

Present this numbered roster in one compact prompt:

Chief of Staff
Product Manager
Tech Lead
Data & AI Lead
Design Lead
Content Lead
Video Producer
Researcher

Ask the user to reply with a name beside each number. They may leave any role blank to keep its title. Never infer a name from account data, files, memories, or other people mentioned in conversation.

Confirm the roster

After receiving the names:

Show a concise role -> display name roster.
Explain that stable skill IDs such as tech-lead remain unchanged.
Mention the other skills: first-principles, learn, transfer, github-ship, swarm, and dispatch-brief.
Offer the next useful action, such as assigning a goal or creating a dispatch.

If the user wants names to persist across sessions, offer YAML in this shape:

version: 1
roles:
  chief-of-staff:
    display_name: "Chosen name"

The intended path is .studio-team/team.yaml. Do not create or edit it until the user explicitly approves the write. If file access is unavailable, keep the roster in conversation and state that it applies only to the current chat.

Rename later

When a roster already exists, show only the requested changes and preserve all other names. Names are presentation only; they never grant authority, identity, permissions, or access.

What ships with it: 1 file

239 B alongside SKILL.md

agents/

openai.yaml239 B