Skip to content
TrustedSkillsbeta
Back to all skills

Gcp Gke Monitoring Observability

Checked
dawiddutoit·vlatest·cloud

Helps with Google Cloud, monitoring as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dawiddutoit/custom-claude --skill gcp-gke-monitoring-observability -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dawiddutoit

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned dawiddutoit/custom-claude at 17b45a90a6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
17b45a90a6
Manifest
skills/gcp-gke-monitoring-observability/SKILL.md
Scanned
3 files, 908 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides the ability to monitor and gain observability into Google Kubernetes Engine (GKE) clusters. It allows for querying metrics, analyzing logs, and identifying potential issues within your GKE environment. The skill leverages GCP's monitoring tools to provide insights into cluster health and application performance.

When to use it

  • Troubleshooting a slow or failing application running in GKE: Use the skill to identify resource bottlenecks or error patterns.
  • Proactively identifying potential problems in your GKE clusters: Monitor key metrics for unusual behavior that might indicate an impending issue.
  • Analyzing the performance of new deployments in GKE: Gain insights into how a new release impacts cluster resources and application response times.
  • Generating reports on GKE resource utilization: Track trends over time to optimize costs and capacity planning.

Key capabilities

  • Metric querying from GKE clusters
  • Log analysis within the GKE environment
  • Identification of performance bottlenecks
  • Cluster health monitoring

Example prompts

  • "Show me CPU usage for my 'production' GKE cluster over the last hour."
  • "What are the error rates for pods in the 'web-app' namespace?"
  • “Analyze logs from the past 24 hours for any errors related to database connections.”

Tips & gotchas

  • Requires appropriate GCP permissions to access and query GKE monitoring data.
  • The skill’s effectiveness depends on proper configuration of logging and metrics collection within your GKE clusters.