Skills gke-expert

📦

gke-expert

Name: gke-expert
Author: AdminTurnedDevOps

Content revision r1 Safe ⚙️ External commands🌐 Network access

Operate GKE Clusters with Expert Guidance

GKE operations can be complex across deployment, scaling, identity, and troubleshooting. This skill provides practical workflows, commands, and production patterns for reliable GKE management.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "gke-expert" from https://skillstore.io/skills/adminturneddevops-gke-expert.md and its manifest at https://skillstore.io/api/skills/adminturneddevops-gke-expert/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/adminturneddevops-gke-expert.md Signed manifest GET /api/skills/adminturneddevops-gke-expert/manifest Signed lockfile GET /api/skills/adminturneddevops-gke-expert/lockfile

Test it

Using "gke-expert". I need to deploy an API on GKE.

Expected outcome:

A cluster type recommendation based on workload requirements.
A deployment and service checklist with placeholders to replace.
Verification steps for rollout, endpoints, and load balancing.

Using "gke-expert". My pod is stuck in CrashLoopBackOff.

Expected outcome:

Log and previous container checks.
Event and resource checks to identify scheduling or memory issues.
Likely remediation paths based on the observed failure mode.

Using "gke-expert". I want to lower GKE costs for staging.

Expected outcome:

Recommendations for Autopilot, autoscaling, Spot VMs, and resource requests.
A review checklist for non-critical workloads.
Warnings about changes that may affect reliability.

Security Audit

Safe

v9 • 7/7/2026 Open versioned report

The static findings are documentation examples, not executable code. The kubectl exec command uses a placeholder for interactive debugging, and the URLs point to official public documentation. No prompt injection, data exfiltration intent, or hidden unsafe behavior was found in the reviewed files.

Files scanned

386

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:191

🌐 Network access (5)

SKILL.md:202 SKILL.md:203 SKILL.md:204 SKILL.md:205 SKILL.md:206

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/adminturneddevops-gke-expert/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/adminturneddevops-gke-expert/security.svg)](https://skillstore.io/skills/adminturneddevops-gke-expert?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/adminturneddevops-gke-expert?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/adminturneddevops-gke-expert/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/adminturneddevops-gke-expert.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

AdminTurnedDevOps. (2026). gke-expert security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/adminturneddevops-gke-expert/audits/9

BibTeX citation

@techreport{adminturneddevops-adminturneddevops-gke-expert-2026,
  author = {AdminTurnedDevOps},
  title = {gke-expert security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/adminturneddevops-gke-expert/audits/9},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gke-expert security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
  - name: "AdminTurnedDevOps"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/adminturneddevops-gke-expert/audits/9"
identifiers:
  - type: other
    value: "skillstore:adminturneddevops-gke-expert:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Launch a GKE workload

Plan a cluster, deploy a container, expose a service, and verify the rollout.

Troubleshoot Kubernetes failures

Investigate pod, service, event, and resource issues with focused GKE checks.

Improve GKE security and cost

Apply Workload Identity, security contexts, autoscaling, and cost controls to a cluster.

Try These Prompts

Create a Basic Cluster Plan

Help me choose between GKE Autopilot and Standard for a small web service. Include the main commands and assumptions.

Deploy and Expose an App

Create a GKE deployment plan for my container image. Include resource limits, service exposure, and verification steps.

Diagnose Production Issues

Guide me through troubleshooting a GKE service with failing pods and no endpoints. Ask for missing context before recommending commands.

Design a Secure GKE Platform

Review my GKE production design for Workload Identity, ingress, autoscaling, disruption budgets, and cost controls.

Best Practices

Confirm cluster type, environment, and risk before changing GKE resources.
Replace placeholders with reviewed project, cluster, namespace, and service names.
Use Workload Identity and least privilege instead of static credentials.

Avoid

Running copied commands against production without checking context and namespace.
Using broad cleanup commands without labels, backups, or rollback plans.
Skipping resource requests, limits, and autoscaling configuration.