klingai-team-setup
Configure Kling AI for teams with per-project API keys, usage quotas, and role-based access. Trigger with phrases like ''klingai team'', ''kling ai organization'', ''klingai multi-user'', ''shared klingai access''. '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill klingai-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.
# Kling AI Team Setup ## Overview Manage team access to the Kling AI API using separate API keys, environment-based routing, usage quotas per team member, and centralized credential management. ## Per-Environment API Keys Create separate API key pairs in the [Kling AI developer console](https://app.klingai.com/global/dev/api-key) for each environment: | Environment | Key Naming Convention | Purpos
What does the klingai-team-setup skill do?
Configure Kling AI for teams with per-project API keys, usage quotas, and role-based access. Trigger with phrases like ''klingai team'', ''kling ai organization'', ''klingai multi-user'', ''shared klingai access''. '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill klingai-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.
