Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.
Orchestrates comprehensive production readiness reviews and assessments for GKE clusters and workloads across scalability, security, reliability, observability, backup/DR, and cost optimization. Use when asked to productionize, prepare
---
name: gke-productionize
metadata:
version: "1.0.0"
category: Containers
description: Orchestrates comprehensive production readiness reviews and assessments for GKE clusters and workloads across scalability, security, reliability, observability, backup/DR, and cost optimization. Use when asked to productionize, prepare, assess, audit, or review a GKE cluster or workload before going live to production. Don't use for deep-dive single-domain implementation (use specific domain skills like gke-workload-scaling, gke-platform-security, gke-workload-security, gke-service-networking, gke-reliability instead).
---
# GKE Productionize Skill
This skill acts as a high-level orchestrator for preparing a GKE cluster and its
workloads for production readiness.
> [!IMPORTANT]
> This is a **meta-skill** or **orchestrator skill**. You are
> expected to invoke and run many other specialized skills listed in this
> document as part of the overall productionization process. Do not attempt to
> implement all production readiness features directly within this skill;
> instead, use this skill to assess the environment and then delegate to the
> specific skills for each domain.
## Scope
This skill is adaptable to:
- A single application (already on Kubernetes or not).
- A set of applications.
- A target cluster.
## Workflow
### 1. Discovery Phase
Before making recommendations, discover the current state of the environment.
#### Cluster Discovery
Run these commands to understand the cluster setup:
- Check cluster details: `gcloud container clusters describe {cluster_name}
--location {location} --project {project}`
- Check for Autopilot vs Standard: Look for the following block in the
describe output:
```yaml
autopilot:
enabled: true
```
- Check release channel: Look for `releaseChannel`.
#### Workload Discovery
If a specific application is targeted, discover its configuration:
- Get deployment/statefulset details: `kubectl get deployment {app_name} -n
{namespace} -o yaml`
- Check for dedicated namespace and labels: `kubectl get namespace {namespace}
-o yaml` (Look for Pod Security Standards labels).
- Check for dedicated service account usage: `kubectl get pods -n {namespace}
-o
custom-columns="NAME:.metadata.name,SERVICE_ACCOUNT:.spec.serviceAccountName"`
- Check for resource requests and limits.
- Check for liveness, readiness, and startup probes.
- Check for HPA: `kubectl get hpa -n {namespace}`
- Check for PDB: `kubectl get pdb -n {namespace}`
- Check for NetworkPolicies: `kubectl get networkpolicy -n {namespace}`
### 2. Production Readiness Assessment
**Before implementation, you MUST run the skills for each relevant specialized
area listed below and incorporate its guidance into your assessment and plan.
Failure to do so will result in a non-compliant production configuration.**
#### A. App Onboarding (Pre-Kubernetes)
If the application is not yet running on GKE, you MUST run the
`gke-app-onboarding` skill for planning containerization, image building, and
basic deployment.
#### B. Scalability & Resource Management
Ensure workloads have appropriate resources and autoscaling.
- **Action**: You MUST run the `gke-workload-scaling` skill for configuring
HPA, VPA, and resource limits.
#### C. Observability
Ensure adequate logging and monitoring are in place.
- **Action**: You MUST run the `gke-observability` skill for setting up Cloud
Logging, Monitoring, and Managed Prometheus.
#### D. Reliability
Ensure high availability and graceful degradation.
- **Action**: You MUST run the `gke-reliability` skill for configuring
regional clusters, PDBs, and health probes.
#### E. Security
Harden the cluster and workloads.
- **Action**: You MUST run the `gke-platform-security` and
`gke-workload-security` skills for Workload Identity, Network Policies, and
Shielded Nodes.
- **Namespace Isolation**: Ensure workloads run in dedicated namespaces with
Pod Security Standards (PSS) enforced via labels.
- **Least Privilege**: Ensure workloads use dedicated ServiceAccounts instead
of the `default` ServiceAccount.
#### F. Backup & Disaster Recovery
Ensure stateful data is protected.
- **Action**: You MUST run the `gke-backup-dr` skill for configuring Backup
for GKE and restore procedures.
#### G. Edge Security & Ingress
Secure external access.
- **Action**: You MUST run the `gke-service-networking` skill for Gateway API,
Ingress, and Cloud Armor.
#### H. Cost Optimization
Ensure efficient use of resources.
- **Action**: You MUST run the `gke-cost-optimization` skill for strategies on
rightsizing, quotas, and Spot VMs.
#### I. Upgrades & Maintenance Posture
Ensure a safe, predictable upgrade posture.
- **Action**: You MUST run the `gke-upgrades` skill for release channel
selection, maintenance windows/exclusions, and node pool upgrade strategy.
#### J. Golden Path Defaults Audit
Ensure the cluster configuration matches recommended defaults.
- **Action**: You MUST run the `gke-golden-path` skill to compare the cluster
against golden path defaults and report deviations with severity and
remediation.
### 3. Production Readiness Scoring
After the assessment, provide a summary report with a RAG (Red, Amber, Green)
status for each area and an overall readiness score. This helps prioritize
remediation efforts.
Apply this rubric deterministically so repeated assessments of the same
environment produce the same result:
1. **Per-domain criteria**: For each assessed domain (A-J), list the concrete
checks performed (from the domain skill's guidance) and classify each check
as **pass**, **fail-critical** (production-blocking, e.g., no resource
requests, no backups for stateful data, public control plane in a locked
down environment), or **fail-minor** (improvement, e.g., missing VPA
recommendations, no Spot usage for batch).
2. **RAG mapping (per domain)**:
- **Red** = one or more fail-critical checks.
- **Amber** = no fail-critical, but one or more fail-minor checks.
- **Green** = all checks pass.
3. **Domain score**: Green = 100, Amber = 50, Red = 0.
4. **Weighted overall score**: weight Security, Reliability, and Backup/DR at
2x; all other assessed domains at 1x. Overall score = sum(domain score x
weight) / sum(weights), rounded to the nearest integer. Exclude domains
that are not applicable (e.g., Backup/DR for fully stateless workloads) from
both sums and note the exclusion.
5. **Readiness verdict**: >= 90 with no Red domains = "Production ready";
70-89 with no Red domains = "Ready with follow-ups"; anything else =
"Not production ready".
In the report, show the per-domain check lists, RAG status, weights, and the
computed overall score.
## Adaptability Guidelines
- **Single App**: Focus on Health Probes, HPA, Resource Limits, PDB, and
Workload Identity for that specific app.
- **Cluster Wide**: Focus on Cluster Autoscaler, Multi-zonal setup, Release
Channels, Maintenance Windows, and default Network Policies.
- **Proactive Execution**: Proactively execute relevant skills (e.g.,
observability, security, scaling, reliability) to assess and propose
improvements, seeking user confirmation before applying state-changing
implementations.
Orchestrates comprehensive production readiness reviews and assessments for GKE clusters and workloads across scalability, security, reliability, observability, backup/DR, and cost optimization. Use when asked to productionize, prepare
Complete original Google guidance with source attribution and declared execution limits.
Use supplied evidence to plan, review or explain the relevant workflow within authorized scope.
Authorized project context, resource scope, current configuration evidence and a named decision owner.
The original is official Apache-2.0 guidance. It may show cloud commands, deployment examples or credential placeholders; those are not run, configured, installed, or authorized by loading this catalog entry. Verify current provider documentation and resource-owner approval before external changes.
Use Google GKE Productionize for [TASK]. Start from authorized project context and supplied evidence. Identify unknowns and propose changes for review; do not run commands, connect accounts, deploy, transfer data, or incur charges from this text alone.
Automatic cloud execution, credential handling, account access, deployments, destructive changes, or claims that examples are configured and verified.
M11 added German routing, integrity tracking and a strict no-execution boundary. Original attribution: Google (google/skills repository). The original is official Apache-2.0 guidance. It may show cloud commands, deployment examples or credential placeholders; those are not run, configured, installed, or authorized by loading this catalog entry. Verify current provider documentation and resource-owner approval before external changes.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Copy the text below, then paste it into your chat.