New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vercel Enterprise Rbac

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure Vercel enterprise RBAC, access groups, SSO integration, and audit logging.

MITAuto-check passedBackend & APIs

Install Vercel Enterprise Rbac

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-enterprise-rbac -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-enterprise-rbac --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/vercel-enterprise-rbac .claude/skills/vercel-enterprise-rbac && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vercel-enterprise-rbac
GitHub stars
2.8k
Token cost
~2k tokens
SKILL.md length
551 words
Files
5 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure Vercel enterprise RBAC, access groups, SSO integration, and audit logging.

  • Works in 6 steps: Understand Vercel's Role Model → Configure Team Members via API → Access Groups (Project-Level Permissions) → …
  • Implementing team access control
  • SKILL.md covers Overview, Prerequisites, Instructions and RBAC Checklist, plus 5 more sections
  • Calls curl and jq; reaches vercel.com and api.vercel.com; needs VERCEL_TOKEN

What it does

Vercel Enterprise Rbac is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Vercel enterprise RBAC, access groups, SSO integration, and audit logging. Use when implementing team access control, configuring SAML SSO, or setting up role-based permissions for Vercel projects. Trigger with phrases like "vercel SSO", "vercel RBAC", "vercel enterprise", "vercel roles", "vercel permissions", "vercel access groups".

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/errors.md`, `references/examples.md` and `references/role-implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Backend & APIs, covering Authorization and RBAC and Authentication. It works with Vercel. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Implementing team access control
  • Configuring SAML SSO
  • Setting up role-based permissions for Vercel projects
  • With phrases like vercel SSO

Example prompts

  • “vercel SSO”
  • “vercel RBAC”
  • “vercel enterprise”
  • “/vercel-enterprise-rbac”

Requirements

  • A credential in VERCEL_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Understand Vercel's Role Model
  2. Configure Team Members via API
  3. Access Groups (Project-Level Permissions)
  4. SSO / SAML Configuration
  5. Application-Level Auth with Middleware
  6. Audit Logging

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • vercel.com
    • api.vercel.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • VERCEL_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Vercel Enterprise Rbac loads about 2k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 551 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 551 words, ~2,031 tokens.

Download SKILL.mdSave it as .claude/skills/vercel-enterprise-rbac/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
vercel-enterprise-rbac
description
Configure Vercel enterprise RBAC, access groups, SSO integration, and audit logging. Use when implementing team access control, configuring SAML SSO, or setting up role-based permissions for Vercel projects. Trigger with phrases like "vercel SSO", "vercel RBAC", "vercel enterprise", "vercel roles", "vercel permissions", "vercel access groups".
allowed-tools
Read, Write, Edit, Bash(curl:*)
compatibility
Designed for Claude Code
version
1.18.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, vercel, rbac, enterprise, sso

Vercel Enterprise RBAC

Overview

Configure Vercel's role-based access control (RBAC) with team roles, project-level access groups, SSO/SAML integration, and audit logging. Covers the two access control planes: team-level (who can deploy) and application-level (who can access deployed content).

Prerequisites

  • Vercel Pro or Enterprise plan
  • Identity Provider (IdP) with SAML 2.0 support (for SSO)
  • Understanding of your organization's access requirements

Instructions

Step 1: Understand Vercel's Role Model

Team-Level Roles:

RoleDeploy ProdManage ProjectsManage BillingManage Members
OwnerYesYesYesYes
MemberYesYesNoNo
DeveloperPreview onlyLimitedNoNo
ViewerNoRead-onlyNoNo
Security (Enterprise)NoSecurity settingsNoNo

Extended Permissions (Enterprise): Layer on top of base roles for granular control:

  • Deploy to production
  • Manage environment variables
  • Manage domains
  • Access runtime logs
  • Manage integrations
Step 2: Configure Team Members via API
bash
# Invite a team member
curl -X POST "https://api.vercel.com/v1/teams/team_xxx/members" \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "developer@company.com",
    "role": "DEVELOPER"
  }'

# List team members
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v2/teams/team_xxx/members" \
  | jq '.members[] | {name: .name, email: .email, role: .role}'

# Update a member's role
curl -X PATCH "https://api.vercel.com/v1/teams/team_xxx/members/user_xxx" \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"role": "MEMBER"}'

# Remove a team member
curl -X DELETE "https://api.vercel.com/v1/teams/team_xxx/members/user_xxx" \
  -H "Authorization: Bearer $VERCEL_TOKEN"
Step 3: Access Groups (Project-Level Permissions)

Access Groups assign teams of people to specific projects with specific roles:

  1. Go to Team Settings > Access Groups
  2. Create a group (e.g., "Frontend Team", "Backend Team")
  3. Add members to the group
  4. Assign the group to specific projects with a role
Example Access Group Setup:
├── Frontend Team → [project-web, project-docs] → Member role
├── Backend Team → [project-api, project-worker] → Member role
├── DevOps Team → [all projects] → Member role
└── QA Team → [all projects] → Viewer role
Step 4: SSO / SAML Configuration

In the Vercel dashboard: Team Settings > Authentication > SAML Single Sign-On

  1. Enable SAML SSO
  2. Configure your IdP (Okta, Azure AD, Google Workspace):
    • ACS URL: https://vercel.com/api/auth/saml/acs
    • Entity ID: https://vercel.com
    • Name ID format: emailAddress
  3. Enter IdP metadata URL or upload certificate
  4. Map SAML attributes to Vercel fields
SAML Attribute Mapping:
├── email → user email (required)
├── firstName → display name
├── lastName → display name
└── groups → Vercel team roles (optional)

Enforce SSO for all team members: Once enabled, toggle "Require SAML for login" — all members must authenticate through SSO.

Step 5: Application-Level Auth with Middleware
typescript
// middleware.ts — enforce auth on deployed application routes
import { NextRequest, NextResponse } from 'next/server';
import { verifyJWT } from '@/lib/auth';

const ROLE_ROUTES: Record<string, string[]> = {
  '/admin': ['admin'],
  '/dashboard': ['admin', 'member'],
  '/api/admin': ['admin'],
};

export async function middleware(request: NextRequest) {
  const { pathname } = request.nextUrl;

  // Check if route requires auth
  const requiredRoles = Object.entries(ROLE_ROUTES)
    .find(([prefix]) => pathname.startsWith(prefix));

  if (!requiredRoles) return NextResponse.next();

  const token = request.cookies.get('session')?.value;
  if (!token) {
    return pathname.startsWith('/api')
      ? NextResponse.json({ error: 'Unauthorized' }, { status: 401 })
      : NextResponse.redirect(new URL('/login', request.url));
  }

  const payload = await verifyJWT(token);
  if (!payload || !requiredRoles[1].includes(payload.role)) {
    return NextResponse.json({ error: 'Forbidden' }, { status: 403 });
  }

  // Pass user info to API routes via headers
  const response = NextResponse.next();
  response.headers.set('x-user-id', payload.sub);
  response.headers.set('x-user-role', payload.role);
  return response;
}

export const config = {
  matcher: ['/admin/:path*', '/dashboard/:path*', '/api/admin/:path*'],
};
Step 6: Audit Logging

Vercel Enterprise includes audit logs in Team Settings > Audit Log.

Events tracked:

  • Team member added/removed/role changed
  • Project created/deleted
  • Deployment to production
  • Environment variable created/updated/deleted
  • Domain added/removed
  • Integration installed/uninstalled
  • SSO configuration changes
bash
# Export audit logs via API (Enterprise)
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v1/teams/team_xxx/audit-log?limit=100" \
  | jq '.events[] | {action: .action, user: .user.email, createdAt: .createdAt, resource: .resource}'

RBAC Checklist

CheckStatus
Team roles assigned per least privilegeRequired
Production deploy restricted to Member+Required
Access Groups configured per projectRecommended
SSO/SAML enforced for all membersEnterprise
Audit logging exported to SIEMEnterprise
Application-level auth in middlewareRequired
Off-boarding removes Vercel access via IdPRequired
Show full SKILL.md (204 more words)Show less

Output

  • Team roles configured with least-privilege access
  • Access Groups scoping members to specific projects
  • SSO/SAML enforced for all team authentication
  • Application-level RBAC in Edge Middleware
  • Audit logs exported for compliance

Error Handling

ErrorCauseSolution
Member can't deploy to prodDeveloper role (preview only)Change to Member or Owner role
SSO login failsIdP metadata URL expiredUpdate SAML configuration
Access Group not appliedMember not in groupAdd member to the Access Group
Audit log missing eventsFree/Pro plan limitationUpgrade to Enterprise for audit logs
Off-boarded user still has accessSSO not enforcedEnable "Require SAML for login"

Examples

Off-board a production deployer with evidence

Remove the person from the identity-provider group that maps to Vercel production access, then confirm their team membership and Access Group assignments no longer grant deployment capability. Keep at least two designated owners in the recovery group before making changes, and test a non-production access path with a substitute account rather than the departed user’s credentials. Export the relevant audit event to the approved SIEM and retain the change ticket identifier without copying user data into the repository.

Resources

Next Steps

For migration strategies, see vercel-migration-deep-dive.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/.curated/vercel-enterprise-rbac of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/errors.md
  • references/examples.md
  • references/role-implementation.md
  • references/sso-integration.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Vercel Enterprise Rbac next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vercel Enterprise Rbac compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vercel Enterprise Rbac this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT
Auth Implementation Patternsynulihao/AgentSkillOS61810 repos~4.4kAutomated safety check: PassNone
Configuration Cryptogreenpau/caddy-security2.3k—~3.5kAutomated safety check: PassApache-2.0
Supercheck Security Authsupercheck-io/supercheck215—~1.2kAutomated safety check: PassAGPL-3.0
Bkend Authww-w-ai/bkit-claude-code601—~937Automated safety check: NotesApache-2.0

Similar skills

  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed

  • Auth Implementation Patterns

    ynulihao/AgentSkillOS

    Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems.

    618 GitHub starsUsed in 10 repos~4.4k tokens
    Backend & APIsAuto-check passed

  • Configuration Crypto

    greenpau/caddy-security

    Configure portal/policy JWT keys, token names and lifetimes, key loading and generation, public-key discovery, and System API encryption keys.

    2.3k GitHub stars~3.5k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed

  • Supercheck Security Auth

    supercheck-io/supercheck

    Work on Supercheck authentication, RBAC, tenant isolation, sessions, API and trigger keys, invitations, project membership, project variables, OAuth, super-admin behavior, SSRF, or…

    215 GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Bkend Auth

    ww-w-ai/bkit-claude-code

    bkend.ai authentication — email/social login, JWT tokens, RBAC, session management.

    601 GitHub stars~937 tokensUpdated 14 days ago
    Backend & APIsAuto-check: notes

  • Authentication

    codewithmukesh/dotnet-claude-kit

    Authentication and authorization for ASP.NET Core. An agent skill from codewithmukesh/dotnet-claude-kit.

    756 GitHub starsUsed in 1 repo~1.9k tokens
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Vercel Enterprise Rbac

What does Vercel Enterprise Rbac do?

Configure Vercel enterprise RBAC, access groups, SSO integration, and audit logging. Vercel Enterprise Rbac is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Vercel enterprise RBAC, access groups, SSO integration, and audit logging.

When should I use Vercel Enterprise Rbac?

Vercel Enterprise Rbac fits situations like: implementing team access control; configuring SAML SSO; setting up role-based permissions for Vercel projects; with phrases like vercel SSO.

How do I install Vercel Enterprise Rbac in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-enterprise-rbac -a claude-code`. Or copy the skill folder (skills/.curated/vercel-enterprise-rbac in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/vercel-enterprise-rbac in your project. Claude Code loads it when a task matches its description.

How do I install Vercel Enterprise Rbac in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-enterprise-rbac -a codex`. Or copy the skill folder (skills/.curated/vercel-enterprise-rbac in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/vercel-enterprise-rbac in your project. Codex loads it when a task matches its description.

Can I use Vercel Enterprise Rbac in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-enterprise-rbac -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vercel-enterprise-rbac, .gemini/skills/vercel-enterprise-rbac, .github/skills/vercel-enterprise-rbac and .opencode/skills/vercel-enterprise-rbac in your project.

What does Vercel Enterprise Rbac need to run?

Going by SKILL.md and its folder, Vercel Enterprise Rbac needs the command-line tools its instructions call (curl and jq) and credentials named VERCEL_TOKEN. Our summary lists: A credential in VERCEL_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Vercel Enterprise Rbac access the network?

SKILL.md names 2 domains. In commands or code: vercel.com and api.vercel.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Vercel Enterprise Rbac safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vercel Enterprise Rbac use?

Vercel Enterprise Rbac is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vercel Enterprise Rbac use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 604 tokens, read only when the agent opens those files.

What are the alternatives to Vercel Enterprise Rbac?

Skills that share tags, products or a category with Vercel Enterprise Rbac: Cognito (itsmostafa/aws-agent-skills, 1.2k stars), Auth Implementation Patterns (ynulihao/AgentSkillOS, 618 stars), Configuration Crypto (greenpau/caddy-security, 2.3k stars) and Supercheck Security Auth (supercheck-io/supercheck, 215 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vercel Enterprise Rbac?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.