Agent skill · security · jeremylongshore
apollo-enterprise-rbac
Enterprise role-based access control for Apollo.io.
Why this skill is useful
Adds a complete implementation for enterprise RBAC with scoped API keys and permission matrices specifically for Apollo.io, which the AI wouldn't generate on its own.
What it needs
Requires node installed locally. Requires apollo account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apollo Enterprise RBAC Overview Role-based access control for Apollo.io API integrations. Apollo API keys are all-or-nothing (standard vs master), so RBAC must be implemented in your application layer as a proxy between users and the Apollo API. This skill builds a permission matrix, scoped API key system, Express middleware, and admin audit endpoints. Prerequisites Apollo master API key Node.js 18+ with Express Instructions Step 1: Define Roles and Permission Matrix Map Apollo API operations to team roles. Apollo's API has two main categories: Read-only: search (free), enrichment (credits) Write: contacts CRUD, sequences, deals, tasks Step 2: Scoped API Key System Step 3: Permission Middleware Step 4: Apollo API Proxy with RBAC Step 5: Admin Endpoints Output Five-tier role system mapping to Apollo API operations Scoped API key creation with configurable TTL and revocation Express middleware enforcing per-endpoint permissions Apollo API proxy routing all requests through RBAC Admin endpoints for key management and usage stats Examples For a new analyst, an authorized administrator issues a time-limited read/enrichment key for that analyst’s team, delivers the plaintext value once through the approved secret channel, and records the key ID, role, expiry, and approver in the audit system. The proxy stores and compares only the key hash, so a database or log export cannot replay the credential. Test the analyst against an allowed search endpoint and a denied sequence-write endpoint. On a role change or suspected exposure, revoke the old key first, verify that the proxy returns 401, then issue a replacement; never edit the permission map or share the Apollo master key to work around a denial. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apollo-enterprise-rbac