Configure OpenRouter for multi-user team environments. Use when setting up shared access or team-level controls. Trigger with phrases like 'openrouter team', 'openrouter multi-user', 'openrouter organization', 'team api keys'.
From openrouter-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin openrouter-packThis skill is limited to using the following tools:
references/access-control.mdreferences/api-key-strategy-for-teams.mdreferences/budget-management.mdreferences/errors.mdreferences/examples.mdreferences/shared-services-setup.mdreferences/team-configuration.mdreferences/tracking-by-user.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
This skill covers configuring OpenRouter for team use, including per-user API key strategies, usage tracking by team member, and shared budget management.
X-Title header with user or team identifiers so usage shows up attributed in the OpenRouter dashboard| Error | Cause | Fix |
|---|---|---|
| User exceeds personal budget | No per-user limits set | Create individual keys with credit limits; implement middleware budget checks |
| Attribution missing | Requests not tagged with user ID | Enforce X-Title header in shared client wrapper; reject untagged requests |
| Key sprawl | Too many keys to manage | Consolidate to service keys with user headers; implement key lifecycle management |
See ${CLAUDE_SKILL_DIR}/references/errors.md for full error reference.
See ${CLAUDE_SKILL_DIR}/references/examples.md for runnable code samples.