Whizard Auditing

94TrustedInstructions only

Kubernetes and KubeSphere audit event collection and storage configuration.

What it does

Whizard Auditing configures the event collection component within the KubeSphere Observability Platform. It guides the assistant in identifying cluster targets, selecting the latest extension versions, and constructing the correct deployment manifests for Kubernetes audit logging.

By installing this skill, your assistant gains the ability to generate specific InstallPlan resources. It manages the required hierarchical structure for audit sinks, such as OpenSearch or Doris, ensuring the configurations meet platform requirements for data processing and storage.

When it earns its place

Reach for it when…

Use this skill when you need to deploy or update the auditing extension across your KubeSphere clusters, or when configuring storage backends like OpenSearch and Doris for captured event data.

Look elsewhere when…

This skill is not suitable for general Kubernetes log management or troubleshooting cluster performance issues. If you are configuring the underlying telemetry data pipeline or the base vector installation, use those respective tools instead.

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.

  • install whizard auditing on my host cluster
  • how do i configure the doris sink for auditing
  • find the latest version of the auditing extension
  • help me create an install plan for whizard auditing

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-auditing ~/.claude/skills/whizard-auditing

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-auditing .claude/skills/whizard-auditing

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