openrouter-team-setup
Configure OpenRouter for multi-user teams with per-user keys, budget controls, and usage attribution. Triggers: ''openrouter team'', ''openrouter multi-user'', ''openrouter organization'', ''team api keys openrouter''. '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill openrouter-team-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OpenRouter Team Setup ## Overview OpenRouter supports team usage through per-user API keys with individual credit limits, management keys for programmatic key provisioning, and usage attribution via headers. This skill covers key provisioning, per-user budgets, usage tracking, and governance policies for multi-user deployments. ## Prerequisites - A management key (`sk-or-v1-...`) with provisioni
What does the openrouter-team-setup skill do?
Configure OpenRouter for multi-user teams with per-user keys, budget controls, and usage attribution. Triggers: ''openrouter team'', ''openrouter multi-user'', ''openrouter organization'', ''team api keys openrouter''. '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill openrouter-team-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
