Catalog
BerriAI/delete-team

BerriAI

delete-team

Delete one or more teams from a live LiteLLM proxy. Ask for the team_id(s) and confirm before calling POST /team/delete.

v1.0LATEST
NewUpdated Oct 12, 2026

Delete Team

Delete one or more teams from a live LiteLLM proxy.

Setup

LITELLM_BASE_URL  — e.g. https://my-proxy.example.com
LITELLM_API_KEY   — proxy admin key

Ask the user

  1. team_id(s) — if they don't have them, list first:
    curl -s "$BASE/team/list" -H "Authorization: Bearer $KEY"
    
  2. Confirm — show the team alias and ask for confirmation before deleting.

Run

curl -s -X POST "$BASE/team/delete" \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"team_ids": ["<team_id>"]}'

Multiple teams: "team_ids": ["id1", "id2"]

Output

Show the deleted_teams list from the response.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

68/100

Grade

C

Adequate

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

72

Quality

62

Clarity

78

Completeness

58

Summary

Delete one or more teams from a live LiteLLM proxy by collecting team IDs from the user, confirming the operation, and calling POST /team/delete. The skill uses curl with bearer token authentication to interact with a LiteLLM proxy API, requiring a base URL and admin API key as environment variables.

Detected Capabilities

HTTP request (curl POST)Environment variable read (LITELLM_BASE_URL, LITELLM_API_KEY)Bearer token authenticationCredential-based API callDestructive operation (team deletion)

Trigger Keywords

Phrases that agents use to match this skill to user intent.

delete litellm teamremove teams proxybulk team deletionlitellm team managementteam cleanup

Risk Signals

WARNING

Environment variable credential access (LITELLM_API_KEY)

Setup section and curl invocation
WARNING

Destructive operation (team deletion) without error handling documented

Run section, curl POST to /team/delete
WARNING

No input validation on team_ids parameter shown

Run section, team_ids template
INFO

Confirmation step described but no specific guard rails shown for implementation

Ask the user section, step 2

Referenced Domains

External domains referenced in skill content, detected by static analysis.

my-proxy.example.com

Use Cases

  • Remove inactive teams from a LiteLLM proxy
  • Bulk delete multiple teams with confirmation
  • Clean up deprecated or test teams from a proxy deployment
  • Automate team lifecycle management in LiteLLM environments

Quality Notes

  • Skill clearly scopes the task to a specific LiteLLM proxy endpoint
  • Setup section explicitly documents required environment variables
  • Provides both single and bulk deletion examples
  • Includes optional list-first workflow for users without team IDs
  • Lacks error handling guidance (e.g., how to handle 401/403 auth errors, non-existent teams)
  • Confirmation step is described but implementation details are sparse — unclear how agent should parse user input or validate team identities before deletion
  • No guidance on rollback, recovery, or audit logging after deletion
  • Missing details on expected response format validation
Model: claude-haiku-4-5-20251001Analyzed: Oct 12, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use BerriAI/delete-team in your dev environment

Command Palette

Search for a command to run...