Skip to content
TrustedSkillsbeta
Back to all skills

Kubernetes_Liveness_Readiness_Probes

Checked
davidcastagnetoa·vlatest·cloud

Automates Kubernetes liveness/readiness probe configuration to ensure application health and resilience.

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 davidcastagnetoa/skills --skill kubernetes_liveness_readiness_probes -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

davidcastagnetoa

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 davidcastagnetoa/skills at bd906f22af.

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

Commit
bd906f22af
Manifest
skills/kubernetes_liveness_readiness_probes/SKILL.md
Scanned
1 file, 175 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 allows AI agents to configure and understand Kubernetes liveness and readiness probes. It enables the agent to define how Kubernetes determines if a container is healthy (liveness) or ready to serve traffic (readiness), ensuring application stability and efficient resource utilization within a cluster. The skill facilitates automated probe configuration based on application requirements.

When to use it

  • Automated Deployment: Configure probes during deployment of new applications to ensure they are properly monitored for health and readiness.
  • Troubleshooting Application Issues: Analyze existing probe configurations to diagnose why an application might be unhealthy or unavailable.
  • Optimizing Resource Allocation: Adjust probe thresholds to fine-tune when Kubernetes restarts failing containers or removes them from service rotation.
  • Self-Healing Clusters: Implement proactive health checks that automatically restart or replace failing pods based on probe results.

Key capabilities

  • Define liveness probes (HTTP GET, TCP socket, Exec command)
  • Define readiness probes (HTTP GET, TCP socket, Exec command)
  • Configure initial delay and period seconds for probes
  • Understand probe failure thresholds

Example prompts

  • "Create a readiness probe for my application that checks the /healthz endpoint."
  • "What is the current liveness probe configuration for pod 'my-app'?"
  • "Set the initial delay to 30 seconds and period to 10 seconds for the liveness probe of container 'web'."

Tips & gotchas

Ensure the probes accurately reflect the application’s health. Incorrectly configured probes can lead to unnecessary restarts or traffic disruption. Understanding your application's dependencies is crucial for defining effective readiness probes.