Loading...
Loading...
Found 196 Skills
Interactive setup guide for using Infisical as a secret management tool in your projects. Helps users integrate Infisical into local development (CLI), Docker containers (build-time and runtime secret injection), CI/CD pipelines (GitHub Actions, GitLab CI), Kubernetes (Operator + CRDs), and application code (all 9 SDKs: Node.js, Python, Go, Java, .NET, Ruby, PHP, Rust, C++). Also walks through choosing and configuring any of the 13 machine identity auth methods (Universal, Token, Kubernetes, GCP, AliCloud, AWS, Azure, TLS Cert, OCI, OIDC, JWT, LDAP, SPIFFE). Use this skill whenever someone asks about: using Infisical, injecting secrets, infisical run, infisical init, connecting their app to Infisical, Docker secrets, Kubernetes secrets operator, machine identity setup, SDK initialization, CI/CD secret injection, or 'how do I get my secrets into my app'. Not for the Kubernetes Operator CRDs (infisical-kubernetes-operator), rendering secrets to files (infisical-agent), pushing secrets outward (infisical-secret-syncs), or human SSO login (infisical-sso).
Reads and manages Gerrit code reviews over the HTTPS REST API: change metadata and diffs, inline comments and drafts, reviewers and CCs, labels and votes, checks, topics, hashtags, commit messages, cherry-picks, abandon, and submit. Use when working with Android (AOSP), Chromium, Fuchsia, or self-hosted Gerrit, when given a Gerrit change URL (https://*-review.googlesource.com/*, https://r.android.com/*, https://crrev.com/c/*, https://fxrev.dev/*, or https://*/c/*/+/*), or when git commands target a Gerrit host (refs/for/ pushes or branch cherry-picks). Don't use for local-only git operations or GitHub and GitLab pull requests.
Adopt the Platform engineering standard in a repository, with or without the Project Health dashboard. Use when a team wants the engineering gates, coverage, mutation, complexity, security, SBOM or hygiene facets, the engineering scorecard, or an engineering-only dashboard, on GitHub, Azure DevOps, GitLab or another host.
Guide for connecting Infisical to an identity provider for human login and user provisioning. Covers Google and GitHub SSO (free), SAML 2.0 and OIDC (paid) with Okta, Azure/Entra ID, JumpCloud, Google, Auth0, Keycloak, PingOne, GitLab, LDAP login, SCIM user and group provisioning with Okta/Azure/JumpCloud/PingOne/PingFederate, SAML and OIDC group membership mapping, SCIM group to organization role mappings, the mandatory email domain verification prerequisite, SSO enforcement and its effect on password signup, and the /login/admin break-glass portal. Use this skill when someone asks about: Infisical SSO, SAML login, OIDC login, Okta or Azure AD integration, SCIM provisioning, syncing identity provider groups into Infisical, enforcing SSO, or being locked out after enabling SSO. For HUMAN login and user provisioning. Not for machine identity auth methods, including OIDC and LDAP for workloads (infisical-setup), nor for roles and permissions (infisical-access-control).
Use when CI (GitHub Actions, Azure Pipelines, GitLab) runs integration tests against the Azure SQL Database container as a service: health check, registry secrets. For Testcontainers, use `azuresql-db-testing`.
Point the user to the code or source behind the previous response, with a snippet plus a link to the exact lines on its forge (GitHub, GitLab, Azure DevOps, Bitbucket, Gitea/Forgejo), a link to the exact section of the source material, or both. Use when the user runs /show-me or asks where something you said comes from.
Vercel deployment and CI/CD expert guidance. Use when deploying, promoting, rolling back, inspecting deployments, building with --prebuilt, or configuring CI workflow files for Vercel.
CI/CD Pipeline Builder
Lance une revue d'issue automatique avec des personas experts sélectionnés automatiquement, analyse la faisabilité, la complétude, les risques et l'architecture, puis publie un rapport structuré directement sur l'issue — le tout sans intervention de l'utilisateur.
List my open MRs/PRs in the current repo/worktree, each with its tracker ticket. Use when I invoke /list-open-work, or ask what I have open, what's in review, or for a standup list of my open MRs or PRs.
Configure CI/CD pipelines for Documenso integrations. Use when setting up automated testing, deployment pipelines, or continuous integration for Documenso projects. Trigger with phrases like "documenso CI", "documenso GitHub Actions", "documenso pipeline", "documenso automated testing".
CI/CD 流水线配置