Django Access Review
getsentry/skills
Django access control and IDOR security review. An agent skill from getsentry/skills.
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces.
$ npx skills add google/skills --skill gke-workload-security -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install google/skills gke-workload-security --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cloud/gke-workload-security .claude/skills/gke-workload-security && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gke-workload-security" agent skill from https://github.com/google/skills/tree/main/skills/cloud/gke-workload-security into .claude/skills/gke-workload-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gke-workload-security", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/google/skills/tree/main/skills/cloud/gke-workload-securityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add google/skills --skill gke-workload-security -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install google/skills gke-workload-security --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cloud/gke-workload-security .agents/skills/gke-workload-security && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gke-workload-security" agent skill from https://github.com/google/skills/tree/main/skills/cloud/gke-workload-security into .agents/skills/gke-workload-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gke-workload-security", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add google/skills --skill gke-workload-security -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install google/skills gke-workload-security --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cloud/gke-workload-security .cursor/skills/gke-workload-security && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gke-workload-security" agent skill from https://github.com/google/skills/tree/main/skills/cloud/gke-workload-security into .cursor/skills/gke-workload-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gke-workload-security", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/google/skills.git --path skills/cloud/gke-workload-security--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add google/skills --skill gke-workload-security -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install google/skills gke-workload-security --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cloud/gke-workload-security .gemini/skills/gke-workload-security && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gke-workload-security" agent skill from https://github.com/google/skills/tree/main/skills/cloud/gke-workload-security into .gemini/skills/gke-workload-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gke-workload-security", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install google/skills gke-workload-securityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add google/skills --skill gke-workload-security -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cloud/gke-workload-security .github/skills/gke-workload-security && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gke-workload-security" agent skill from https://github.com/google/skills/tree/main/skills/cloud/gke-workload-security into .github/skills/gke-workload-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gke-workload-security", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add google/skills --skill gke-workload-security -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install google/skills gke-workload-security --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cloud/gke-workload-security .opencode/skills/gke-workload-security && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gke-workload-security" agent skill from https://github.com/google/skills/tree/main/skills/cloud/gke-workload-security into .opencode/skills/gke-workload-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gke-workload-security", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
gke-workload-securityAudits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces.
Gke Workload Security is an agent skill from google/skills, published by the product's own GitHub organization. Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod Security Standards (restricted labeling) and pod securityContext, and mounting Secret Manager secrets via CSI (SecretProviderClass). Use when auditing workload security posture, isolating namespaces…
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and assets (for example `assets/default-deny-netpol.yaml`, `assets/workload-identity-pod.yaml` and `scripts/audit_cluster.sh`).
It sits in Backend & APIs, covering Authorization and RBAC and Security review. It works with Google Kubernetes Engine. The repository describes itself as: Agent Skills for Google products and technologies. The licence is Apache-2.0.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8a1ac05. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
kubectlgcloudFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
cloud.google.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Gke Workload Security loads about 1.9k tokens when it runs. Until then it costs about 216 tokens; SKILL.md has 563 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from google/skills at commit 8a1ac05, republished under its Apache-2.0 licence (© google). 563 words, ~1,939 tokens.
.claude/skills/gke-workload-security/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Routing Note: For Workload Identity KSA/GSA bindings, open
gke-workload-identity/SKILL.md. For cluster-level security flags (--database-encryption-key,--security-posture, RBAC, Shielded Nodes, Binary Authorization), opengke-platform-security/SKILL.md.
This skill provides workflows and best practices for securing GKE workloads. It covers security auditing, Identity and Access Management (Workload Identity), Network Security (Network Policies), and Node Security.
Assess the current security posture of your cluster using the provided audit script.
Prerequisites:
gcloud CLI authenticated.jq command-line JSON processor installed.Capabilities:
Command:
scripts/audit_cluster.sh <cluster-name> <region> <project-id>Workload Identity allows Kubernetes Service Accounts (KSAs) to impersonate Google Service Accounts (GSAs). This is the recommended method for workloads to access Google Cloud APIs.
Steps:
Create Namespace and KSA:
kubectl create namespace workload-identity-test-ns
kubectl create serviceaccount <ksa-name> \
--namespace workload-identity-test-nsBind KSA to GSA:
gcloud iam service-accounts add-iam-policy-binding <gsa-name>@<project-id>.iam.gserviceaccount.com \
--role roles/iam.workloadIdentityUser \
--member "serviceAccount:<project-id>.svc.id.goog[workload-identity-test-ns/<ksa-name>]"Annotate KSA:
kubectl annotate serviceaccount <ksa-name> \
--namespace workload-identity-test-ns \
iam.gke.io/gcp-service-account=<gsa-name>@<project-id>.iam.gserviceaccount.comVerify Example Pod: Use existing asset
assets/workload-identity-pod.yaml to test the configuration. Update the
<ksa-name> in the file first.
kubectl apply -f assets/workload-identity-pod.yaml -n workload-identity-test-nsControl traffic flow between Pods using Network Policies. By default, all traffic is allowed.
Enable Network Policy Enforcement:
gcloud container clusters update <cluster-name> \
--update-addons=NetworkPolicy=ENABLED \
--region <region>[!NOTE] If your cluster uses Dataplane V2 (
--enable-dataplane-v2), Network Policy enforcement is built-in and this step is not required (and may fail).
Apply Default Deny Policy: Isolate namespaces by denying all ingress and egress traffic by default.
Replace <target-namespace> with the namespace you want to isolate.
kubectl apply -f assets/default-deny-netpol.yaml -n <target-namespace>Run untrusted workloads in a sandbox for extra kernel isolation. (Note:
Enabling Shielded Nodes (--enable-shielded-nodes) and GKE Sandbox
(--enable-gke-sandbox) at the cluster control plane level are platform-level
actions covered in the gke-platform-security skill.)
Run a Sandboxed Pod: Add runtimeClassName: gvisor to your Pod spec:
apiVersion: v1
kind: Pod
metadata:
name: sandboxed-pod
spec:
runtimeClassName: gvisor
containers:
- name: app
image: nginxEnforce security policies on namespaces using labels.
Enforce Restricted Profile:
kubectl label --overwrite ns <namespace> \
pod-security.kubernetes.io/enforce=restricted \
pod-security.kubernetes.io/enforce-version=latest[!NOTE] Using
latestensures you use the policies corresponding to the cluster's current version. You can pin it to a specific version (e.g.,v1.30) to lock down the namespace to policies of a specific release.
Mount secrets from Google Cloud Secret Manager directly as volumes in your pods.
Prerequisites: Secret Manager CSI driver must be enabled on the cluster.
Example SecretProviderClass:
apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
name: my-secret-provider
spec:
provider: gcp
parameters:
secrets: |
- resourceName: "projects/<project-id>/secrets/my-secret/versions/latest"
fileName: "my-secret-file"Example Pod Spec excerpt:
spec:
containers:
- name: my-app
volumeMounts:
- name: secrets-store-inline
mountPath: "/mnt/secrets"
readOnly: true
volumes:
- name: secrets-store-inline
csi:
driver: secrets-store.csi.k8s.io
readOnly: true
volumeAttributes:
secretProviderClass: "my-secret-provider"If using GKE Dataplane V2, you can log allowed and denied connections.
Steps:
NetworkLogging custom resource.Example NetworkLogging Manifest:
apiVersion: networking.gke.io/v1alpha1
kind: NetworkLogging
metadata:
name: default
spec:
cluster:
allow:
log: true
delegate: true
deny:
log: true
delegate: trueThis will log connection details to Cloud Logging.
baseline or restricted Pod Security Standards
on all non-system namespaces.© google, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts, assets) in skills/cloud/gke-workload-security of google/skills.
Open the folder on GitHubat commit 8a1ac05
Gke Workload Security next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gke Workload Security this skillgoogle/skills | 21k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Django Access Reviewgetsentry/skills | 1k | 3 repos | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Cb Security HardeningBlkLeg/CircuitBreaker | 201 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Implementing Conditional Access Policies Azure Admukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~689 | Automated safety check: Pass | Apache-2.0 | |
| Sec Checkwaynesutton/markdown-site | 628 | — | ~753 | Automated safety check: Pass | MIT | |
| Security Hardeningchmonitor/chmonitor | 298 | — | ~440 | Automated safety check: Pass | GPL-3.0 |
getsentry/skills
Django access control and IDOR security review. An agent skill from getsentry/skills.
BlkLeg/CircuitBreaker
Enforces Circuit Breaker security hardening conventions across backend, frontend, Docker, and nginx.
mukul975/Anthropic-Cybersecurity-Skills
Configures Microsoft Entra ID (Azure AD) Conditional Access policies for zero trust access control, covering signal-based policy design, device compliance requirements, risk-based authentication…
waynesutton/markdown-site
Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code.
chmonitor/chmonitor
RBAC configuration, row policies, quotas, network security, audit logging, and access control best practices.
ZeroDeng01/sublinkPro
Checklist-driven security review for changes to authentication, authorization, MFA, secrets, input validation and other security-critical code.
google/skills
Manages Google Cloud Privileged Access Manager entitlements and grants: create and edit entitlements, request temporary access, and approve or deny pending grants.
google/skills
Writes Terraform alerting policies for AI agents that emit OpenTelemetry metrics, covering reliability, cost, safety, security and quality signals on Google Cloud.
google/skills
Deploys open models or custom weights from Model Garden to Agent Platform endpoints, checks deployment status and cleans up endpoints, confirming before any change.
google/skills
Searches, manages and scaffolds skills in the Gemini Enterprise Agent Platform Skill Registry using bundled Python scripts and Google Cloud credentials.
google/skills
Designs GCP infrastructure as local Terraform, validates and scans it against best practices, then imports it to Application Design Center for deployment and troubleshooting.
google/skills
Analyzes BigQuery slot use, query costs and execution bottlenecks from INFORMATION_SCHEMA to diagnose slow queries, slot contention and unpartitioned scans.
Works with
Categories
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Gke Workload Security is an agent skill from google/skills, published by the product's own GitHub organization. Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces.
Gke Workload Security fits situations like: auditing workload security posture; isolating namespaces; applying pod security standards; configuring network policies and secret volume mounts.
Run `npx skills add google/skills --skill gke-workload-security -a claude-code`. Or copy the skill folder (skills/cloud/gke-workload-security in google/skills) into .claude/skills/gke-workload-security in your project. Claude Code loads it when a task matches its description.
Run `npx skills add google/skills --skill gke-workload-security -a codex`. Or copy the skill folder (skills/cloud/gke-workload-security in google/skills) into .agents/skills/gke-workload-security in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add google/skills --skill gke-workload-security -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gke-workload-security, .gemini/skills/gke-workload-security, .github/skills/gke-workload-security and .opencode/skills/gke-workload-security in your project.
Going by SKILL.md and its folder, Gke Workload Security needs a shell for the scripts in its folder and the command-line tools its instructions call (kubectl and gcloud). Our summary lists: A Bash shell.
SKILL.md names 1 domain. As links in the text: cloud.google.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Gke Workload Security is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Gke Workload Security: Django Access Review (getsentry/skills, 1k stars), Cb Security Hardening (BlkLeg/CircuitBreaker, 201 stars), Implementing Conditional Access Policies Azure Ad (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Sec Check (waynesutton/markdown-site, 628 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
google (a GitHub organization, an official publisher) maintains it in google/skills, which has 20,994 GitHub stars. The repository holds 145 skills in this directory. The repository was last updated on October 6, 2026.
Source: google/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.