Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/algolia-enterprise-rbac

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-enterprise-rbac

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈74 tokens for metadata: the name and description. ≈855 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈296 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Identify excessive grants, orphaned credentials, or tenant escape paths and propose bounded remediation.

Approval Boundaries

Do not enable SSO, change team roles, revoke keys, or alter tenant filters without owner approval and a tested recovery path.

Output

Return the actor matrix, role and ACL mapping, current-plan evidence, denied-path tests, lifecycle controls, findings, and remediation approvals.

Error Handling

Condition Response
Feature absent from current account Record it as unavailable; do not infer entitlement.
Actor requires broad ACL Split duties or document the exceptional grant.
Secured key has no restriction Reject generation.
Role change risks lockout Prepare and test break-glass access first.

Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

actor=catalog-indexer; operations=save,settings; indices=products_*

Expected handoff:

key=custom; ACL=minimum-reviewed; tenant-browser=secured-key; sso=contract-verified

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides instructions and references for auditing Algolia Enterprise RBAC and API key configurations. It focuses on assessing least-privilege access and SSO requirements. While it involves reading local code and configuration, which is a standard surface for indirect prompt injection, no malicious patterns or high-risk behaviors were identified.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [application-or-role]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "access-control"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-enterprise-rbac