update-team
Skill84 starsChanged 7 months agoMITView on GitHub
Update an existing team on a live LiteLLM proxy. Ask for the team_id and what to change (budget, models, limits), then call POST /team/update.
- Reads credentials
- Sends data out
2 other projects use a version of this.
Adopted by
Most recently taken up by
- OpenRouterTeam/spawntheir own version, first seen Oct 8, 2026
- OpenRouterLabs/spawntheir own version, first seen Jun 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- OpenRouterLabs/spawn★ 251same name
- OpenRouterTeam/spawn★ 251same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- add-agentSkill
- add-keySkill
- add-mcpSkill
- add-modelSkill
- add-orgSkill
- add-teamSkill
- 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-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 16
Update an existing team on a live LiteLLM proxy.
- Distinctive: line 54
Only include the fields being changed.
≈ “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
Update Team
Update an existing team on a live LiteLLM proxy.
Setup
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_id (required) — if they don't have it, list teams first:
curl -s "$BASE/team/list" -H "Authorization: Bearer $KEY" - What to change — any combination of:
team_alias(string)max_budget(float)models(list)tpm_limit/rpm_limit(int)blocked(bool — blocks all requests from this team)
Run
curl -s -X POST "$BASE/team/update" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"team_id": "<team_id>",
"max_budget": <value>,
"models": [<models>],
"tpm_limit": <value>
}'Only include the fields being changed.
Output
Show the updated team_id, team_alias, max_budget, models.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

