agentleFS
BerriAIBerriAI/litellm-skills/add-team/SKILL.md

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

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
  1. Distinctive:

    Create a new team on a live LiteLLM proxy.

    line 14
  2. Distinctive:

    Ask for these if not already known:

    line 18

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 key

API reference: https://litellm.vercel.app/docs/proxy/team_based_routing

Ask the user

  1. Team name (required, becomes team_alias)
  2. Max budget (optional, e.g. 100.00)
  3. Allowed models (optional, e.g. gpt-4o, gpt-4o-mini) — leave empty to allow all
  4. 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 team
  • team_alias, max_budget, models

On error:

  • 401 — check that LITELLM_API_KEY is a valid admin key
  • 400 — check required fields (team_alias is required)
  • Other errors — show detail and the likely fix

Download now (ZIP)

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.