Agent skill · software engineering · jeremylongshore
adobe-enterprise-rbac
Govern Adobe Developer Console roles, product profiles, technical accounts, User Management API automation, and periodic access review. Use when the task requires adobe enterprise access governance. Trigger with "Adobe RBAC", "Adobe product profiles", or "Adobe user provisioning".
Why this skill is useful
Provides specific SCIM provisioning commands and Adobe User Management API patterns that the AI wouldn't reliably generate on its own.
What it needs
Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Enterprise Access Governance Overview Govern Adobe Developer Console roles, product profiles, technical accounts, User Management API automation, and periodic access review. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract Developer Console project access, API scopes, product entitlement, product-profile assignment, and resource ownership are distinct. User Management API manages enterprise users/groups/entitlements under its own authorization; it is not a generic fix for application API access. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use named admin/automation identities with least privilege, environment binding, approver separation, rotation, and review dates. Technical-account access is constrained by assigned product profiles. Instructions 1. Inventory organizations, directories, admins, developers, projects, credentials, users/groups, products, profiles, and automation. 2. Build a role-to-operation matrix and calculate effective access across Console roles, scopes, profiles, and resources. 3. Identify orphaned credentials, broad profiles, stale users, shared admins, and cross-environment grants. 4. Design joiner/mover/leaver and service-account changes with approval, idempotency, reconciliation, and rollback. 5. Canary UMAPI changes on a synthetic group where authorized and compare intended versus effective access. 6. Schedule recertification, exception expiry, secret rotation, audit export, and emergency revocation. Tool Discipline Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-enterprise-rbac