add-team
Skill84 starsChanged 7 months agoMITView on GitHub
Create 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.
- Reads credentials
- Sends data out
In this repository20 other files it gives its agents.
- add-agentSkill
- add-keySkill
- add-mcpSkill
- add-modelSkill
- add-orgSkill
- add-userSkill
- delete-agentSkill
- delete-keySkill
- delete-mcpSkill
- delete-modelSkill
- delete-orgSkill
- delete-teamSkill
- delete-userSkill
- update-agentSkill
- update-keySkill
- update-mcpSkill
- update-modelSkill
- update-teamSkill
- update-userSkill
- view-usageSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Create a new team on a live LiteLLM proxy.
- Distinctive: line 18
Ask for these if not already known:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Team
Create a new team on a live LiteLLM proxy.
Setup
Ask for these if not already known:
LITELLM_BASE_URL — e.g. https://my-proxy.example.com
LITELLM_API_KEY — proxy admin keyAPI reference: https://litellm.vercel.app/docs/proxy/team_based_routing
Ask the user
- Team name (required, becomes
team_alias) - Max budget (optional, e.g.
100.00) - Allowed models (optional, e.g.
gpt-4o, gpt-4o-mini) — leave empty to allow all - TPM / RPM limits (optional)
Run
BASE="$LITELLM_BASE_URL"
KEY="$LITELLM_API_KEY"
curl -s -X POST "$BASE/team/new" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"team_alias": "<name>",
"max_budget": <budget_or_null>,
"models": [<models_or_empty>],
"tpm_limit": <tpm_or_null>,
"rpm_limit": <rpm_or_null>
}'Verify
Confirm the team was created:
curl -s "$BASE/team/info?team_id=<team_id>" \
-H "Authorization: Bearer $KEY"Output
Show the user:
team_id— they'll need this to generate keys for the teamteam_alias,max_budget,models
On error:
- 401 — check that
LITELLM_API_KEYis a valid admin key - 400 — check required fields (team_alias is required)
- Other errors — show
detailand the likely fix
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

