add-key
Skill84 starsChanged 7 months agoMITView on GitHub
Generate a new API key on a live LiteLLM proxy. Asks for alias, scope (user/team), budget, models, and expiry, then calls POST /key/generate. Use when the user wants to create, generate, or provision an API key on a LiteLLM proxy instance.
- Reads credentials
- Sends data out
In this repository20 other files it gives its agents.
- add-agentSkill
- add-mcpSkill
- add-modelSkill
- add-orgSkill
- add-teamSkill
- add-userSkill
- delete-agentSkill
- delete-keySkill
- delete-mcpSkill
- delete-modelSkill
- delete-orgSkill
- delete-teamSkill
- delete-userSkill
- update-agentSkill
- update-keySkill
- update-mcpSkill
- update-modelSkill
- update-teamSkill
- update-userSkill
- view-usageSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 18
Ask for these if not already known:
≈ “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.
Files
Add Key
Generate a new API key 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 keyAPI reference: https://litellm.vercel.app/docs/proxy/virtual_keys
Ask the user
- Key alias (optional but recommended, e.g.
my-app-prod) - Scope — assign to a
team_idoruser_id? (optional) - Allowed models (optional, e.g.
gpt-4o, claude-3-5-sonnet) - Max budget (optional, e.g.
5.00) - Expiry (optional, e.g.
7d,30d,90d) — omit for no expiry
Run
BASE="$LITELLM_BASE_URL"
KEY="$LITELLM_API_KEY"
curl -s -X POST "$BASE/key/generate" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"key_alias": "<alias>",
"team_id": "<team_id_or_omit>",
"user_id": "<user_id_or_omit>",
"models": [<models_or_empty>],
"max_budget": <budget_or_null>,
"duration": "<duration_or_omit>"
}'Verify
Confirm the key was created:
curl -s "$BASE/key/info" \
-H "Authorization: Bearer <new_key>" | python3 -c "
import sys, json
d = json.load(sys.stdin)
info = d.get('info', {})
print(f'Alias: {info.get(\"key_alias\")}')
print(f'Expires: {info.get(\"expires\")}')
print(f'Budget: {info.get(\"max_budget\")}')
print(f'Models: {info.get(\"models\")}')
"Output
Show the user:
key— the actual key value (only shown once, tell them to save it)key_alias,expires,max_budget,models
On error:
- 401 — check that
LITELLM_API_KEYis a valid admin key - 400 — check required fields; verify
team_id/user_idexists - Other errors — show
detailand the likely fix
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

