← Explore all skills

IDENTITY AND ACCESS / Infisical Inc.

Infisical Access Control and Governance Guide

Infisical skill for deciding what a user or machine identity may do inside Infisical: org and project roles, granular secret permissions, ABAC, temporary access, approval policies and audit log streams.

“Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by user metadata and machine identity attributes, additional privileges, assume-privilege, temporary (time-bound) access, access requests, change-approval and access-approval policies, and audit logs including streaming to Splunk, Datadog, Azure, Cribl, Sumo Logic, or a custom webhook. Use this skill when someone asks about: Infisical roles and permissions, custom roles, least privilege for secrets, letting someone see a secret exists without reading it, ABAC, temporary access, approval workflows for secret changes, access requests, audit logs, or streaming audit events to a SIEM. For what a principal can do once inside. Not for connecting an identity provider for login or SCIM (infisical-sso), nor for machine identity auth methods (infisical-setup).”

01 / THE REASONING

Why this made the selection.

  • It separates describeSecret (seeing that a secret exists and its metadata) from readValue (seeing the value), and warns that the legacy read action grants both.
  • It draws the line with infisical-sso explicitly: SSO decides who gets in, this skill decides what they can do once inside, and PAM and PKI role models go to their own skills.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • skills/infisical-access-control/SKILL.md
  • skills/infisical-access-control/references/approvals-and-audit.md
  • README.md
  • LICENSE
  • .claude-plugin/marketplace.json

Our findings

  • It treats no-access as a real role in both the org and project role sets, used to keep a member enrolled without granting anything.
  • It says to assign roles to groups, not people, so joiners and leavers are handled by the identity provider.
  • It warns that blanket approval on every change produces rubber-stamping, and scopes approval policies per environment and path.

Not established by this review

  • Not executed: it was not installed or run.
  • No Infisical role, approval policy, access request or audit log stream was created.
  • references/roles-and-permissions.md was not read; references/approvals-and-audit.md was read only for its opening plan statement.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗
  1. The README's universal install, npx skills add Infisical/ai-skills, names the whole Infisical/ai-skills repository, which the README says holds 17 skills; no file at the pin prints a line that installs infisical-access-control alone.
  2. For Claude Code the README prints /plugin marketplace add Infisical/ai-skills. That adds the infisical-ai-skills marketplace, whose .claude-plugin/marketplace.json lists infisical-access-control as its own plugin (source ./infisical-access-control, plugin root ./plugins); no file at the pin prints the line that installs that plugin.
  3. For a manual install the README says to copy skill folders from skills/ into the agent's skills directory; for this skill that is skills/infisical-access-control/, copied to .claude/skills/ (Claude Code), ~/.codex/skills/ (Codex), .cursor/skills/ or .agents/skills/ (Cursor), or .github/skills/ (GitHub Copilot).
  4. The README recommends Infisical's hosted docs MCP at https://infisical.com/docs/mcp ahead of the skills; that is a separate server and does not install infisical-access-control.

Before you start

  • For approval workflows and access requests: Infisical Cloud Enterprise tier, or an enterprise license when self-hosted

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/Infisical/ai-skills/blob/d7e7fa443893d7ba10895f926407da27751ea096/skills/infisical-access-control/SKILL.md

    Supports: name, upstreamDescription, summary, whySelected, bestFor, limitations, review.findings, access.label, access.permissions, install.prerequisites

  2. https://github.com/Infisical/ai-skills/blob/d7e7fa443893d7ba10895f926407da27751ea096/skills/infisical-access-control/references/approvals-and-audit.md

    Supports: limitations, install.prerequisites, access.cost

  3. README.md at d7e7fa44 ↗Checked

    https://github.com/Infisical/ai-skills/blob/d7e7fa443893d7ba10895f926407da27751ea096/README.md

    Supports: install.command, install.sourceUrl, install.steps, compatibility, summary

  4. LICENSE at d7e7fa44 ↗Checked

    https://github.com/Infisical/ai-skills/blob/d7e7fa443893d7ba10895f926407da27751ea096/LICENSE

    Supports: license, publisher, access.cost

  5. https://github.com/Infisical/ai-skills/blob/d7e7fa443893d7ba10895f926407da27751ea096/.claude-plugin/marketplace.json

    Supports: install.steps

  6. https://github.com/Infisical/ai-skills/tree/d7e7fa443893d7ba10895f926407da27751ea096/skills/infisical-access-control

    Supports: access.permissions, review.findings

  7. https://github.com/Infisical/ai-skills/commit/da9176b6b14d73b6925464215aa310bb800643be

    Supports: limitations

Evidence & Ask