RepoAI
Browse MCPs

Whizard Logging

94TrustedInstructions only

Log collection configuration and API querying for the KubeSphere platform.

What it does

Whizard Logging provides the necessary guidance to deploy and manage log collection services within a KubeSphere cluster environment. It helps assistants understand how to coordinate log pipelines, ranging from container standard output capture to file-based disk logging.

Installing this skill allows an assistant to interpret configuration requirements and translate them into valid InstallPlan manifests. It serves as a bridge between high-level observability goals and the specific YAML structure required by the telemetry extension.

When it earns its place

Reach for it when…

Use this skill when preparing to deploy the telemetry logging extension, determining appropriate cluster targets, or when drafting the correct YAML schemas for log sidecars and sink configurations.

Look elsewhere when…

This skill does not perform administrative tasks related to the underlying OpenSearch instance or the Vector data pipeline itself. It is also unsuitable for troubleshooting network connectivity or authentication issues between your logging stack and external storage.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • How do I set up WizTelemetry Logging on my clusters?
  • Show me the latest version of the logging extension.
  • Help me build an InstallPlan for disk log collection.
  • Which clusters have logging enabled?

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/whizard-logging ~/.claude/skills/whizard-logging

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/kubesphere/skills/whizard-logging .claude/skills/whizard-logging

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

Whizard Logging changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →