Skip to content
TrustedSkillsbeta
Back to all skills

Tzurot Deployment

Checked
lbds137·vlatest·devops·MIT

Automates deployment of containerized applications to tzurot clusters using lbds137's optimized configuration scripts.

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 lbds137/tzurot --skill tzurot-deployment -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

lbds137

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 lbds137/tzurot at db576a093b.

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

Commit
db576a093b
Manifest
.claude/skills/tzurot-deployment/SKILL.md
Scanned
1 file, 247 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

The tzurot-deployment skill automates deployments to Kubernetes clusters. It handles tasks such as building container images, pushing them to a registry, and applying Kubernetes manifests. This streamlines the process of releasing new versions of applications and ensures consistency across environments.

When to use it

  • Deploying a new version of an application: Automate the entire release pipeline from code commit to running containers.
  • Rolling back deployments: Quickly revert to a previous stable version in case of issues.
  • Creating development or staging environments: Easily spin up temporary environments for testing and experimentation.
  • Automating infrastructure changes: Apply updates to Kubernetes resources like services, ingress controllers, and more.

Key capabilities

  • Container image building
  • Image registry pushing
  • Kubernetes manifest application
  • Deployment rollback functionality

Example prompts

  • "Deploy the latest version of my 'my-app' service."
  • "Roll back the 'my-app' deployment to version 1.2.3."
  • "Apply the Kubernetes manifests located in /path/to/manifests."

Tips & gotchas

  • Requires access to a Kubernetes cluster and container registry.
  • Ensure your AI agent has appropriate permissions within the Kubernetes environment for deployments.