infisical-access-control — Claude Code skill: roles and audit
A reference skill for Infisical access control: roles, narrow secret permissions, time-bound access, approval policies and audit log streaming.
MIT 267 installs ★ 41 updated 2026-10-19
npx skills add Infisical/ai-skills --skill infisical-access-control -a claude-codeWhat infisical-access-control does
The agent gets a guide to Infisical's governance layer: which role a person or machine should hold, how to narrow what they can touch, and where audit evidence ends up. Handy while you set up least privilege and would rather not click through every settings page.
Two reference files hold the detail. One covers roles and permissions, from org and project roles through custom roles built out of subjects and actions, the granular secret actions, ABAC conditions, additional privileges, assume-privilege and time-bound access. The other covers approvals and audit: change-approval and access-approval policies, access requests, and log streams to Splunk, Datadog, Azure, Cribl, Sumo Logic or a custom webhook.
Mind the split between describeSecret and readValue. The older read action grants both at once, so a role that should list secrets without exposing values needs the narrow one instead. And when the question is about an identity provider for login or SCIM provisioning, that belongs to infisical-sso; this skill stays on what a principal can do after they are in.
What it helps with
- scope a role so someone sees a secret exists without reading it
- attach ABAC conditions driven by user attributes
- put an expiry on production access instead of granting it forever
- require review before a secret change goes through
- ship audit events to the SIEM your team already watches
Example prompts for the agent
- Set up a contractor role that can list secrets in
productionwithout reading their values. - Give an engineer time-bound access to secrets and show me where the expiry is configured.
- Stream audit logs to Splunk and scope change approval to the
productionenvironment.
How to install infisical-access-control
1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-access-control -a claude-code2Manually: put the files in place
~/.claude/skills/infisical-access-control/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/infisical-access-control/
1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-access-control -a codex2Manually: put the files in place
.agents/skills/infisical-access-control/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-access-control -a cursor2Manually: put the files in place
.cursor/skills/infisical-access-control/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Infisical/ai-skills skills/infisical-access-control2Manually: put the files in place
.github/skills/infisical-access-control/SKILL.md1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-access-control -a gemini-cli2Platform CLI
gemini skills install https://github.com/Infisical/ai-skills --path skills/infisical-access-controlManually: put the files in place
.devin/skills/infisical-access-control/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-access-control -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about infisical-access-control
How to install infisical-access-control in Claude Code?
Run npx skills add Infisical/ai-skills --skill infisical-access-control -a claude-code. The skill lands at ~/.claude/skills/infisical-access-control/SKILL.md.
What does infisical-access-control do?
It walks the agent through Infisical roles and permissions: built-in and custom roles, granular secret actions, ABAC, temporary access, approval policies and audit logs.
Does it cover SSO or SCIM group provisioning?
No. Connecting an identity provider for login and provisioning users is infisical-sso. This skill handles what a principal can do once inside, including the roles those groups map onto.
Source text
SKILL.md · MIT
--- name: infisical-access-control description: "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)." --- # Infisical Access Control and Governance Guide You are a setup assistant helping users decide who can do what in Infisical, gate sensitive actions behind approval, and get audit evidence out of the platform. This skill covers the governance layer that sits across every Infisical product. ## Not this skill | If the user wants... | Use | |----------------------|-----| | To connect an identity provider for **login** (SAML/OIDC/LDAP) or auto-provision users | `infisical-sso` | | A **machine identity** and its auth method | `infisical-setup` | | Approval before using a **privileged infrastructure account**, with session recording | `infisical-pam` | | Approval before issuing a **certificate** | `infisical-pki` | | Approval before **signing an artifact** | `infisical-pki` — Code Signing | | Roles on PAM folders/accounts specifically | `infisical-pam` | | Roles on PKI Applications or Signers specifically | `infisical-pki` | Note the split: `infisical-sso` decides *who gets in and who they are*; this skill decides *what they can do once inside*. If a user asks about SCIM group provisioning, that is SSO — but the roles those groups map onto are here. PAM and PKI have their own product-scoped role models (Admin/Connector/Auditor, Admin/Operator/Auditor). Route role questions about those products to their own skills. ## How to use this skill 1. **Start from the least-privilege question**: what is the smallest thing this principal needs? 2. **Reach for a built-in role first** — custom roles are maintenance 3. **Use granular secret actions** where "can read the value" is too much 4. **Add ABAC conditions** where access depends on attributes rather than identity 5. **Prefer temporary over permanent** for anything sensitive 6. **Gate changes with approval policies** where a mistake is expensive 7. **Stream audit logs** to wherever the security team already looks ## Reference files | File | When to read | |------|-------------| | `references/roles-and-permissions.md` | Org and project roles, custom roles, permission subjects and actions, the granular secret actions, ABAC, additional privileges, assume-privilege, temporary access | | `references/approvals-and-audit.md` | Change-approval and access-approval policies, access requests, audit logs, audit log streams and their 6 providers | ## Guiding principles - **`read` on secrets is coarser than people expect.** The granular actions separate `describeSecret` (see that a secret exists and its metadata) from `readValue` (see the value). The legacy `read` grants **both**. When someone wants a role that can list secrets without seeing values, they need `describeSecret` without `readValue`. - **Assign roles to groups, not people.** Then joiners and leavers are handled by the identity provider. See `infisical-sso` for group provisioning. - **Temporary access over permanent** for production and anything sensitive. Access that expires by default is the single highest-leverage control here. - **Approval policies are per environment and path.** Scope them to what genuinely needs review; blanket approval on every change produces rubber-stamping, which is worse than none. - **`no-access` is a real role.** Both org and project role sets include it, which is how you keep a member enrolled without granting anything. - **Audit logs are only useful if someone sees them.** Stream them out; do not leave them to be read in the UI after an incident. - **Never widen permissions to make an error go away.** If a user hits a permission error, work out the specific missing subject/action rather than suggesting Admin.
© Infisical · MIT · Infisical/ai-skills