Agent skill · marketing growth · jeremylongshore
algolia-enterprise-rbac
Map workforce roles and application actors to Algolia team permissions, API-key ACLs, and secured-key restrictions. Use when reviewing least privilege, tenancy, SSO requirements, or access rotation. Trigger with "Algolia RBAC", "Algolia SSO", or "Algolia tenant access".
Why this skill is useful
Provides specific implementation patterns for configuring Algolia's enterprise RBAC that the AI wouldn't reliably generate on its own.
What it needs
Requires algolia account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Algolia Enterprise Access Design Overview This skill separates human dashboard access, backend service access, browser search access, and tenant-scoped access. It verifies current account capabilities instead of assuming every plan exposes the same roles or SSO features. Prerequisites A named repository, environment, and Algolia application or index in scope The local lockfile and installed client types as implementation authority A safe read-only query or explicitly disposable test target Current first-party documentation for any provider behavior that affects the change Tool Discipline Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan. Current Contract Treat current dashboard settings and contracted features as the authority for workforce roles and SSO availability. Map service operations to documented API-key ACLs and index restrictions. Generate secured search keys only on a trusted backend and require at least one restriction. Model application tenancy in filters and key restrictions; do not confuse that model with provider workforce RBAC. Authentication Review key descriptions, ACLs, restrictions, owners, and rotation dates without exporting secret values. Production services should use organization-owned, least-privilege keys. Instructions 1. Inventory human roles, service identities, browser clients, environments, indices, and tenant boundaries. 2. Capture current provider roles and SSO features from the account or contract, marking unavailable evidence. 3. Map each actor to operations, ACLs, index restrictions, validity, and credential owner. 4. Test denied and allowed operations using safe targets and redacted evidence. 5. Document joiner, mover, leaver, key rotation, break-glass, and audit-review procedures. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-enterprise-rbac