SkillRepo
Sign InSign Up
Catalog
BerriAI/delete-key

BerriAI

delete-key

Delete one or more API keys from a live LiteLLM proxy. Ask for the key(s) and confirm before calling POST /key/delete.

v1.0LATEST
NewUpdated Oct 12, 2026

Delete Key

Delete one or more API keys 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. Key(s) (sk-...) or key alias(es) — if they don't have them, list first: 
    curl -s "$BASE/key/list?size=25&return_full_object=true" -H "Authorization: Bearer $KEY"
  2. Confirm — show the key alias and ask for confirmation before deleting.

Run

By key value:

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

By alias:

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

Output

Show the deleted_keys list from the response.

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

78

Quality

68

Clarity

78

Completeness

62

Summary

This skill guides an agent to delete API keys from a LiteLLM proxy server via authenticated HTTP POST requests. The agent prompts the user for key identifiers or aliases, optionally lists keys first, requests confirmation, and then calls the proxy's `/key/delete` endpoint with the user-approved keys.

Detected Capabilities

http-requestuser-input-promptconfirmation-requestcredential-handling

Trigger Keywords

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

delete api keysrevoke litellm keysremove proxy credentialsdecommission api keylitellm key management

Risk Signals

INFO

Credential handling: LITELLM_API_KEY environment variable required for proxy authentication

Setup section
INFO

Outbound HTTP POST to external proxy endpoint (my-proxy.example.com)

Run section
INFO

Requires user confirmation before destructive operation (key deletion)

Ask the user section

Referenced Domains

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

my-proxy.example.com

Use Cases

  • Delete compromised or unused API keys from a LiteLLM proxy
  • Revoke access by removing specific key aliases from production
  • Clean up test keys after development or testing cycles
  • Decommission keys during employee offboarding or service migrations

Quality Notes

  • Skill clearly defines setup requirements with environment variable names and example values
  • Instructions include two deletion methods (by key value and by alias) with copy-paste-ready curl commands
  • User confirmation step documented, which mitigates accidental deletions
  • Response handling specified (show deleted_keys from response)
  • Skill provides optional listing command if user doesn't have key identifiers, reducing friction
  • No error handling documented for failed deletions, network errors, or invalid key formats
  • No guidance on how to verify keys before deletion or recover from mistakes
  • No examples of successful response structure or failure modes
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-key in your dev environment

Start a Developer trial

Command Palette

Search for a command to run...