SkillRepo
Sign InSign Up
Catalog
BerriAI/delete-user

BerriAI

delete-user

Delete one or more users from a live LiteLLM proxy. Ask for the user_id(s) and confirm before calling POST /user/delete.

v1.0LATEST
NewUpdated Oct 12, 2026

Delete User

Delete one or more users 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. user_id(s) — if they don't have them, list first: 
    curl -s "$BASE/user/list?page_size=25" -H "Authorization: Bearer $KEY"
  2. Confirm — show the user email/alias and ask for confirmation before deleting.

Run

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

Multiple users: "user_ids": ["id1", "id2"]

Output

Show how many users were deleted. Warn if any IDs were not found.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

B

Good

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

Safety

72

Quality

68

Clarity

82

Completeness

65

Summary

This skill guides an AI agent to delete one or more users from a live LiteLLM proxy by accepting user IDs, optionally listing existing users, requesting confirmation, and calling the POST /user/delete endpoint via curl. It requires LiteLLM proxy admin credentials and enforces a confirmation step before destructive operations.

Detected Capabilities

shell execution (curl)http request (POST)credential usage (API key header)environment variable readlist/query operation (user list endpoint)

Trigger Keywords

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

delete litellm userremove proxy userbulk delete userslitellm user managementproxy admin operations

Risk Signals

WARNING

Destructive operation (user deletion) via API without persistent audit trail documented

Run section, POST /user/delete endpoint
WARNING

Credential exposure via environment variable LITELLM_API_KEY passed in Authorization header

Setup section
WARNING

No mention of rollback, backups, or data recovery procedures after deletion

Output section
INFO

Outbound HTTP request to external proxy domain (my-proxy.example.com)

Setup section example URL

Referenced Domains

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

my-proxy.example.com

Use Cases

  • Delete a single user account from LiteLLM proxy by ID
  • Bulk delete multiple users from LiteLLM proxy
  • List existing users before selecting which to delete
  • Confirm user identity (email/alias) before deleting to prevent accidents

Quality Notes

  • Strengths: confirmation step before deletion reduces accidental data loss; clear setup instructions with environment variables; provided curl command examples are well-formatted and unambiguous.
  • Strengths: skill scope is narrow and focused (user deletion only); allowed-tools field correctly restricts to curl.
  • Weaknesses: no error handling guidance for failed deletions, invalid user IDs, or authorization failures.
  • Weaknesses: no documentation of what 'deleted' means (soft delete vs. hard delete, data retention, recovery options).
  • Weaknesses: missing edge cases — behavior with non-existent user IDs, duplicate IDs in bulk delete, partial failures in multi-user requests.
  • Weaknesses: no guidance on auditing or logging deletions for compliance; no mention of backup verification before deletion.
  • Weaknesses: example domain is placeholder but not clearly marked as such (could confuse users about real endpoints).
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-user in your dev environment

Start a Developer trial

Command Palette

Search for a command to run...