Agent skill · marketing growth · jeremylongshore
cohere-enterprise-rbac
Map Cohere Team Owner and User roles to application authorization, key ownership, tenant isolation, and audit controls. Use when governing multi-team Cohere access. Trigger with "Cohere RBAC", "Cohere team roles", or "Cohere enterprise keys".
Why this skill is useful
Adds specific implementation patterns for managing API keys and access control in Cohere that the AI wouldn't reliably generate on its own.
What it needs
Requires cohere account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cohere Enterprise Access Control Overview Use Cohere's documented Team roles for platform administration while enforcing fine-grained workload authorization in the application and secret manager. Prerequisites The target repository, runtime, environment, and accountable owner An approved Cohere team and key for any live verification Current quality, security, privacy, capacity, and change-control requirements Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content. Current Contract Cohere Teams document Owner and User roles; Owners have additional membership, production-key, billing, and production-form powers. Team users can still have broad key and usage capabilities, so provider roles alone are not application RBAC. Separate human administration from runtime service identities and environment-specific credentials. Enforce tenant, model, endpoint, tool, and budget policy before provider calls. Authentication Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place COAPIKEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions. Instructions 1. Inventory Cohere teams, members, roles, keys, environments, service identities, and billing owners. 2. Map Owner and User capabilities to least-privilege job functions and separation-of-duties requirements. 3. Move runtime keys into approved secret stores and bind retrieval to named workloads. 4. Implement application authorization for tenant data, allowed models, endpoints, tools, and spend. 5. Review membership, keys, usage, invoices, and access evidence on a fixed cadence. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-enterprise-rbac