$npx -y skills add BerriAI/litellm-skills --skill add-teamCreate a new team on a live LiteLLM proxy. Asks for team name, budget, and allowed models, then calls POST /team/new and shows the result. Use when the user wants to create a new team, set up team budgets, or configure model access for a team on the proxy.
| 1 | # Add Team |
| 2 | |
| 3 | Create a new team on a live LiteLLM proxy. |
| 4 | |
| 5 | ## Setup |
| 6 | |
| 7 | Ask for these if not already known: |
| 8 | ``` |
| 9 | LITELLM_BASE_URL — e.g. https://my-proxy.example.com |
| 10 | LITELLM_API_KEY — proxy admin key |
| 11 | ``` |
| 12 | |
| 13 | API reference: https://litellm.vercel.app/docs/proxy/team_based_routing |
| 14 | |
| 15 | ## Ask the user |
| 16 | |
| 17 | 1. **Team name** (required, becomes `team_alias`) |
| 18 | 2. **Max budget** (optional, e.g. `100.00`) |
| 19 | 3. **Allowed models** (optional, e.g. `gpt-4o, gpt-4o-mini`) — leave empty to allow all |
| 20 | 4. **TPM / RPM limits** (optional) |
| 21 | |
| 22 | ## Run |
| 23 | |
| 24 | ```bash |
| 25 | BASE="$LITELLM_BASE_URL" |
| 26 | KEY="$LITELLM_API_KEY" |
| 27 | |
| 28 | curl -s -X POST "$BASE/team/new" \ |
| 29 | -H "Authorization: Bearer $KEY" \ |
| 30 | -H "Content-Type: application/json" \ |
| 31 | -d '{ |
| 32 | "team_alias": "<name>", |
| 33 | "max_budget": <budget_or_null>, |
| 34 | "models": [<models_or_empty>], |
| 35 | "tpm_limit": <tpm_or_null>, |
| 36 | "rpm_limit": <rpm_or_null> |
| 37 | }' |
| 38 | ``` |
| 39 | |
| 40 | ## Verify |
| 41 | |
| 42 | Confirm the team was created: |
| 43 | ```bash |
| 44 | curl -s "$BASE/team/info?team_id=<team_id>" \ |
| 45 | -H "Authorization: Bearer $KEY" |
| 46 | ``` |
| 47 | |
| 48 | ## Output |
| 49 | |
| 50 | Show the user: |
| 51 | - `team_id` — they'll need this to generate keys for the team |
| 52 | - `team_alias`, `max_budget`, `models` |
| 53 | |
| 54 | On error: |
| 55 | - **401** — check that `LITELLM_API_KEY` is a valid admin key |
| 56 | - **400** — check required fields (team_alias is required) |
| 57 | - Other errors — show `detail` and the likely fix |