How do I install the Gke Compute Class Creator skill?

Run npx skillmds@latest add tomevault-io/gke-compute-class-creator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gke Compute Class Creator safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gke Compute Class Creator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gke Compute Class Creator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gke Compute Class Creator?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gke Compute Class Creator by tomevault-io

Name: Gke Compute Class Creator
Author: tomevault-io

Gke Compute Class Creator

Guide for creating GKE ComputeClass resources. Use this skill when users want to define custom node configurations, autoscaling priorities, or hardware requirements (e.g., Spot VMs, GPUs, specific machine families) for their GKE workloads. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Creating GKE ComputeClasses

This skill helps you construct ComputeClass resources for Google Kubernetes Engine (GKE). ComputeClasses allow for declarative node configuration and sophisticated autoscaling behaviors like fallback priorities and active migration.

Workflow

Analyze Requirements: Determine the user's goals (Cost optimization? Specific hardware? High availability?).
Select Strategy:
- Cost Optimization: Use spot: true as a high priority, with spot: false as a fallback.
- Performance: Select specific machineFamily (e.g., c3, c4) or machineType.
- AI/ML: Configure gpu or tpu fields.
Construct YAML: Use the references below to build the ComputeClass manifest.
Validate: Ensure all fields comply with the specification.
Apply: Provide the user with the kubectl apply -f <filename>.yaml command.

References

Specification: Detailed breakdown of the ComputeClass CRD fields (priorities, machineFamily, gpu, etc.).
Examples: Copy-pasteable YAML patterns for common scenarios (Spot fallback, GPU, Zonal).

Usage Tips

Active Migration: If the user wants to automatically move back to Spot VMs when they become available, ensure spec.activeMigration.optimizeRulePriority is set to true.
Node Selection: Remind the user that to use the class, their Pods must specify:
```
nodeSelector:
  cloud.google.com/compute-class: "<class-name>"
```
Conflict Warning: Advise against mixing ComputeClass selection with other hard node selectors (like cloud.google.com/gke-spot) as this can lead to scheduling conflicts.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: gke-compute-class-creatordescription: Guide for creating GKE ComputeClass resources. Use this skill when users want to define custom node configurations, autoscaling priorities, or hardware requirements (e.g., Spot VMs, GPUs, specific machine families) for their GKE workloads. Use when this capability is needed.---# Creating GKE ComputeClassesThis skill helps you construct `ComputeClass` resources for Google Kubernetes Engine (GKE). ComputeClasses allow for declarative node configuration and sophisticated autoscaling behaviors like fallback priorities and active migration.## Workflow1. **Analyze Requirements**: Determine the user's goals (Cost optimization? Specific hardware? High availability?).2. **Select Strategy**: - **Cost Optimization**: Use `spot: true` as a high priority, with `spot: false` as a fallback. - **Performance**: Select specific `machineFamily` (e.g., `c3`, `c4`) or `machineType`. - **AI/ML**: Configure `gpu` or `tpu` fields.3. **Construct YAML**: Use the references below to build the `ComputeClass` manifest.4. **Validate**: Ensure all fields comply with the specification.5. **Apply**: Provide the user with the `kubectl apply -f <filename>.yaml` command.## References- **[Specification](references/compute-class-spec.md)**: Detailed breakdown of the `ComputeClass` CRD fields (`priorities`, `machineFamily`, `gpu`, etc.).- **[Examples](references/compute-class-examples.md)**: Copy-pasteable YAML patterns for common scenarios (Spot fallback, GPU, Zonal).## Usage Tips- **Active Migration**: If the user wants to automatically move back to Spot VMs when they become available, ensure `spec.activeMigration.optimizeRulePriority` is set to `true`.- **Node Selection**: Remind the user that to use the class, their Pods must specify: ```yaml nodeSelector: cloud.google.com/compute-class: "<class-name>" ```- **Conflict Warning**: Advise against mixing `ComputeClass` selection with other hard node selectors (like `cloud.google.com/gke-spot`) as this can lead to scheduling conflicts.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/googlecloudplatform) — claim your Tome and manage your conversions.

Frequently asked questions