BerriAI/delete-orgv1.0

delete-org

Delete one or more organizations from a live LiteLLM proxy. Ask for the organization_id(s) and confirm before calling DELETE /organization/delete.

v1.0LATEST

NewUpdated Oct 12, 2026

Delete Organization

Delete one or more organizations 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

organization_id(s) — if they don't have them, list first:

curl -s "$BASE/organization/list" -H "Authorization: Bearer $KEY"

Confirm — show the org alias and ask for confirmation before deleting.

Run

curl -s -X DELETE "$BASE/organization/delete" \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"organization_ids": ["<org_id>"]}'

Output

Show the deleted org ID(s) and alias(es) from the response.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

Good

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

Safety

Quality

Clarity

Completeness

Summary

This skill guides an AI agent to delete one or more organizations from a live LiteLLM proxy by calling the DELETE /organization/delete API endpoint. It requires the agent to collect organization IDs from the user, optionally list existing organizations, confirm the deletion action, and then execute the deletion request using curl with Bearer token authentication.

Detected Capabilities

shell execution (curl)network request (DELETE)bearer token authenticationfile/environment variable referenceuser input confirmation

Trigger Keywords

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

delete litellm organizationremove organization proxylitellm org cleanupbulk delete organizationsorganization deletion confirmation

Risk Signals

WARNING

DELETE request to live proxy with user-provided organization IDs — destructive operation without explicit confirmation logic documented

Run section

WARNING

Bearer token stored in LITELLM_API_KEY environment variable — credentials access required for operation

Setup section

INFO

No error handling documented for failed DELETE requests or invalid organization IDs

Run section

INFO

No rollback or recovery guidance if deletion fails midway through bulk operation

Overall skill

Referenced Domains

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

my-proxy.example.com

Use Cases

Delete a single organization from a LiteLLM proxy after confirming with the user
Bulk delete multiple organizations from a LiteLLM proxy with user confirmation
List organizations before deletion to help the user identify the correct organization_id(s)
Remove deprecated or unused organizations from a LiteLLM proxy environment

Quality Notes

Skill clearly scopes its purpose: delete organizations from LiteLLM proxy
Good practice: asks user to confirm before executing destructive operation
Optional listing step helps user identify correct organization IDs before deletion
Setup section clearly documents required environment variables (LITELLM_BASE_URL, LITELLM_API_KEY)
Allowed tools are correctly restricted to curl-only Bash operations
Missing: error handling guidance — what if the API returns 400, 401, 403, or 500?
Missing: response parsing guidance — how should the agent interpret error vs. success responses?
Missing: guidance on handling partial failures in bulk deletion (e.g., first org deletes successfully, second fails)
Missing: warning about potential data loss — organizations may contain users, API keys, or other resources
Output section mentions 'from the response' but doesn't document the response schema
Documentation is minimal but sufficient for basic operation

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-org in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.

Start a Developer trial