Agent skill · marketing growth · jeremylongshore
instantly-enterprise-rbac
Govern Instantly workspace members, API-key scopes, audit logs, and workspace-group delegation. Use when reviewing access or preparing an owner-approved membership, role, or delegated-workspace change. Trigger with "audit Instantly access", "review Instantly API scopes", or "delegate an Instantly workspace".
Why this skill is useful
Provides specific API commands and governance patterns for managing team access and permissions in Instantly.ai that the AI wouldn't reliably generate on its own.
What it needs
Requires instantly account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Instantly Workspace Access Governance Overview Review and change access with least privilege, explicit ownership, and tenant-boundary evidence. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result. Prerequisites The target repository, Instantly workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved API v2 key only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output. Current Contract API v2 keys support granular resource/action scopes and can be revoked. Workspace groups let an admin key act for a sub-workspace through x-as-workspace. Only owners/admins can manage group membership, and only owners can leave a group. Authentication Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions. Instructions 1. Inventory members, roles, API keys, scopes, service owners, and last-use evidence. 2. Map each automation to the narrowest read/create/update/delete scope set. 3. Review audit logs and flag orphaned, broad, shared, or cross-workspace credentials. 4. For sub-workspace actions, validate the target ID and x-as-workspace header before execution. 5. Prepare member/key/group changes as a reviewed change set. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-enterprise-rbac