New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

mecak8s Kind Manual Verification

by stacklok in stacklok/mecatl

Rebuilds the mecak8s image into the local mecatl-dev Kind cluster and builds mecatui, so you can try in-progress mecatl changes against a real Kubernetes deployment.

Apache-2.0Auto-check passedDevOps & Cloud

Install mecak8s Kind Manual Verification

skills CLI
$ npx skills add stacklok/mecatl --skill mecak8s-kind-manual-verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install stacklok/mecatl mecak8s-kind-manual-verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/stacklok/mecatl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mecak8s-kind-manual-verify .claude/skills/mecak8s-kind-manual-verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mecak8s-kind-manual-verify
GitHub stars
254
Token cost
~927 tokens
SKILL.md length
413 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Rebuilds the mecak8s image into the local mecatl-dev Kind cluster and builds mecatui, so you can try in-progress mecatl changes against a real Kubernetes deployment.

  • Works in 3 steps: Refresh the mecak8s image with current… → Build mecatui locally → Connect and drive it manually
  • Trying an open mecatl pull request against a real Kubernetes deployment
  • SKILL.md covers Prerequisites, Step 1 — Refresh the mecak8s…, Step 2 — Build mecatui locally and Step 3 — Connect and drive it…, plus 3 more sections
  • Calls kind and go; needs OPENROUTER_API_KEY

What it does

This skill is the iterate step of a manual testing loop for mecatl changes, such as an open pull request branch. It assumes a Kind cluster named `mecatl-dev` already exists and does not provision one. Step one runs `task mecak8s:image-refresh`, which rebuilds the `mecak8s` image from the current source with ko, loads it into the running Kind node and does a rolling restart of the deployment in the `mecatl` namespace, waiting up to 240 seconds. It is safe to repeat after every code change and keeps cluster and Redis state.

Step two builds `bin/mecatui` with `task build` instead of a bare go build. Step three connects: the base fixture exposes gRPC and HTTP on local ports, checked with `task mecak8s:kind-status`, and a fixture with the optional Keycloak layer uses the kind-login and kind-connect tasks. Prerequisites are ko, kubectl, kind and either docker or podman, with a Podman environment variable for Podman hosts. The excerpt is cut off partway through the connection step.

When your agent uses it

  • Trying an open mecatl pull request against a real Kubernetes deployment
  • Redeploying the mecak8s image after each code change
  • Building mecatui locally to click through a change by hand

Example prompts

  • “Refresh the mecak8s image in my kind cluster with the current branch and build mecatui.”
  • “I changed the session handling. Deploy it to kind so I can test it manually.”
  • “Check the status of the mecatl-dev fixture and tell me which ports are exposed.”

Requirements

  • ko, kubectl, kind and either docker or podman
  • An existing Kind cluster named mecatl-dev
  • The mecatl repository with its task runner

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Refresh the mecak8s image with current source
  2. Build mecatui locally
  3. Connect and drive it manually

What it can do on your machine

Read from SKILL.md and the folder at commit c6d7338. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • kind
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENROUTER_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

mecak8s Kind Manual Verification loads about 927 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 413 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~927

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from stacklok/mecatl at commit c6d7338, republished under its Apache-2.0 licence (© stacklok). 413 words, ~927 tokens.

Download SKILL.mdSave it as .claude/skills/mecak8s-kind-manual-verify/SKILL.md (or your agent's skills folder).
name
mecak8s-kind-manual-verify
description
Refresh the mecak8s image in the local mecatl-dev Kind cluster and build mecatui locally, so the user can manually verify in-flight mecatl changes against a real k8s deployment.

mecak8s Kind manual verification loop

Use this when the user wants to manually exercise in-progress mecatl changes (e.g. an open PR branch) against a real mecak8s deployment, rather than only relying on offline tests. This is the "deploy to kind and build mecatui so I can click around" loop — fast iteration, not a fresh cluster bring-up.

This assumes a Kind cluster named mecatl-dev already exists (see deploy/mecak8s-kind/README.md for first-time setup via task mecak8s:kind-setup). This skill is for the iterate step, not initial provisioning.

Prerequisites

  • Working directory is the mecatl repo (or a worktree of it).
  • ko, kubectl, kind, and either docker or podman installed.
  • The mecatl-dev Kind cluster already exists (kind get clusters shows it). If it doesn't, run task mecak8s:kind-setup first — that's provisioning, not this skill's job.

Step 1 — Refresh the mecak8s image with current source

From the repo root:

sh
task mecak8s:image-refresh

This rebuilds ko.local/mecak8s:dev from the current source tree via ko build --local --bare --tags=dev ./cmd/mecak8s, loads it straight into the running mecatl-dev Kind node (no cluster teardown), and does a rolling restart of deployment/mecak8s-mecak8s in the mecatl namespace, waiting up to 240s for the rollout to complete.

Use KIND_EXPERIMENTAL_PROVIDER=podman task mecak8s:image-refresh on a Podman host (must match whatever kind-setup was run with).

This is safe to re-run after every code change you want to test — it does not reset cluster/Redis state.

Step 2 — Build mecatui locally

sh
task build

Produces bin/mecatui (along with bin/mecated, bin/mecademo) via the Taskfile — never a bare go build at the repo root, which drops stray binaries.

Show full SKILL.md (164 more words)Show less

Step 3 — Connect and drive it manually

Base fixture (no Keycloak) exposes gRPC at 127.0.0.1:18080 and HTTP at 127.0.0.1:18081 via static Kind NodePort mappings — check with:

sh
task mecak8s:kind-status

If the fixture was set up with the optional Keycloak/OIDC identity layer (task mecak8s:kind-keycloak-setup), log in and connect with the prebuilt shorthand tasks:

sh
task mecak8s:kind-login     # adds /etc/hosts aliases (sudo, once), refreshes fixture CA, runs `mecatui login`
task mecak8s:kind-connect   # adds /etc/hosts aliases, refreshes fixture CA, runs `mecatui connect`

Both require ./bin/mecatui to already exist (Step 2) and task mecak8s:kind-keycloak-setup to have been run at least once. See the keycloak-kind-setup skill if the Keycloak layer itself needs (re-)provisioning or debugging.

Without the Keycloak layer, connect directly:

sh
./bin/mecatui connect 127.0.0.1:18080

Iterating

Repeat Step 1 (task mecak8s:image-refresh) after each code change, then reconnect with mecatui (Step 3) — no need to rebuild mecatui itself unless the TUI/client code changed.

Cleanup

This skill never tears the cluster down. To destroy the whole fixture:

sh
task mecak8s:kind-destroy

Reference

  • deploy/mecak8s-kind/Taskfile.yml — image-refresh, kind-status, kind-login, kind-connect, kind-destroy task definitions.
  • deploy/mecak8s-kind/README.md — full fixture lifecycle, provider modes (mock vs. real via OPENROUTER_API_KEY), and the optional Keycloak layer.
  • keycloak-kind-setup skill — for provisioning/recovering the Keycloak layer itself, if this fixture uses it.

© stacklok, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/mecak8s-kind-manual-verify of stacklok/mecatl.

Open the folder on GitHubat commit c6d7338

Compare with similar skills

mecak8s Kind Manual Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

mecak8s Kind Manual Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
mecak8s Kind Manual Verification this skillstacklok/mecatl254—~927Automated safety check: PassApache-2.0
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Debug Openshell ClusterNVIDIA/OpenShell16k—~20kAutomated safety check: NotesApache-2.0
Aspire MonitoringCommunityToolkit/Aspire627—~3.5kAutomated safety check: PassMIT
Deploymentmatrixorigin/memoria610—~1.6kAutomated safety check: NotesApache-2.0
Chatqna Helm Deployopen-edge-platform/edge-ai-libraries171—~2.3kAutomated safety check: PassApache-2.0

Similar skills

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    16k GitHub stars~20k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Aspire Monitoring

    CommunityToolkit/Aspire

    ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.

    627 GitHub stars~3.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Deployment

    matrixorigin/memoria

    Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.

    610 GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Chatqna Helm Deploy

    open-edge-platform/edge-ai-libraries

    Deploy Chat Question-and-Answer Core to Kubernetes using Helm (OpenVINO CPU, OpenVINO GPU, or Ollama), including values.yaml configuration, helm install/upgrade, deployment verification, uninstall…

    171 GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Onboarding Validation

    open-edge-platform/edge-ai-suites

    Validate the get-started experience of Open Edge Platform (OEP) software components from the perspective of a first-time user.

    140 GitHub stars~3.3k tokensUpdated today
    DevOps & CloudAuto-check passed

More from stacklok/mecatl

All 8 skills in this repo

  • Mecatl Model Router Config

    stacklok/mecatl

    Interviews you about provider, cost, openness and image needs, then designs the models section of a mecatl settings file with aliases, slots and router categories.

    254 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • mecatl Offline Performance Optimization

    stacklok/mecatl

    Runs mecatl's offline benchmark and scenario harness to measure, profile with pprof, optimize and prove a performance win with benchstat, then adds a regression benchmark.

    254 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Mecatl Release Cutting

    stacklok/mecatl

    Cuts a tagged mecatl release by dispatching the release-PR workflow, merging the bot's pull request and verifying the tag, images, Helm chart, signed archives and Homebrew formula.

    254 GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • mecatl Learning Config

    stacklok/mecatl

    Designs, validates and writes the learning section of a mecatl settings file, covering mode, sensitivity, reflection budgets and validated or evaluated activation.

    254 GitHub stars~3.8k tokensUpdated today
    Auto-check passed

  • Mecatl Perf MCP Interpretation

    stacklok/mecatl

    Guides reading mecatl's perf MCP data to find why a running harness is slow, leaking goroutines or growing in memory, using cheap reads before any CPU capture.

    254 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Tech Writer

    stacklok/mecatl

    A skill your agent uses when writing or substantively editing user-facing documentation: drafting a new page, rewriting or restructuring an existing one, adding a major section, or turning…

    254 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about mecak8s Kind Manual Verification

What does mecak8s Kind Manual Verification do?

Rebuilds the mecak8s image into the local mecatl-dev Kind cluster and builds mecatui, so you can try in-progress mecatl changes against a real Kubernetes deployment. This skill is the iterate step of a manual testing loop for mecatl changes, such as an open pull request branch. It assumes a Kind cluster named `mecatl-dev` already exists and does not provision one.

When should I use mecak8s Kind Manual Verification?

mecak8s Kind Manual Verification fits situations like: trying an open mecatl pull request against a real Kubernetes deployment; redeploying the mecak8s image after each code change; building mecatui locally to click through a change by hand.

How do I install mecak8s Kind Manual Verification in Claude Code?

Run `npx skills add stacklok/mecatl --skill mecak8s-kind-manual-verify -a claude-code`. Or copy the skill folder (.claude/skills/mecak8s-kind-manual-verify in stacklok/mecatl) into .claude/skills/mecak8s-kind-manual-verify in your project. Claude Code loads it when a task matches its description.

How do I install mecak8s Kind Manual Verification in Codex?

Run `npx skills add stacklok/mecatl --skill mecak8s-kind-manual-verify -a codex`. Or copy the skill folder (.claude/skills/mecak8s-kind-manual-verify in stacklok/mecatl) into .agents/skills/mecak8s-kind-manual-verify in your project. Codex loads it when a task matches its description.

Can I use mecak8s Kind Manual Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stacklok/mecatl --skill mecak8s-kind-manual-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mecak8s-kind-manual-verify, .gemini/skills/mecak8s-kind-manual-verify, .github/skills/mecak8s-kind-manual-verify and .opencode/skills/mecak8s-kind-manual-verify in your project.

What does mecak8s Kind Manual Verification need to run?

Going by SKILL.md and its folder, mecak8s Kind Manual Verification needs the command-line tools its instructions call (kind and go) and credentials named OPENROUTER_API_KEY. Our summary lists: ko, kubectl, kind and either docker or podman; An existing Kind cluster named mecatl-dev; The mecatl repository with its task runner.

Does mecak8s Kind Manual Verification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is mecak8s Kind Manual Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does mecak8s Kind Manual Verification use?

mecak8s Kind Manual Verification is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does mecak8s Kind Manual Verification use?

About 927 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to mecak8s Kind Manual Verification?

Skills that share tags, products or a category with mecak8s Kind Manual Verification: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Debug Openshell Cluster (NVIDIA/OpenShell, 16k stars), Aspire Monitoring (CommunityToolkit/Aspire, 627 stars) and Deployment (matrixorigin/memoria, 610 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains mecak8s Kind Manual Verification?

stacklok (a GitHub organization) maintains it in stacklok/mecatl, which has 254 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 10, 2026.

Source: stacklok/mecatl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.