Alloy
grafana/skills
Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…
Installs and configures the WizTelemetry Notification extension for KubeSphere: channel setup, alert routing by tenant labels, silences and troubleshooting.
Install WizTelemetry Notification
$ npx skills add kubesphere/kubesphere --skill whizard-notification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kubesphere/kubesphere whizard-notification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/whizard-notification .claude/skills/whizard-notification && rm -rf skills-srcUse ~/.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/
Install the "whizard-notification" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notification into .claude/skills/whizard-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-notification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kubesphere/kubesphere --skill whizard-notification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kubesphere/kubesphere whizard-notification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/whizard-notification .agents/skills/whizard-notification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "whizard-notification" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notification into .agents/skills/whizard-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-notification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kubesphere/kubesphere --skill whizard-notification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kubesphere/kubesphere whizard-notification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/whizard-notification .cursor/skills/whizard-notification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "whizard-notification" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notification into .cursor/skills/whizard-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-notification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kubesphere/kubesphere.git --path skills/whizard-notification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kubesphere/kubesphere --skill whizard-notification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kubesphere/kubesphere whizard-notification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/whizard-notification .gemini/skills/whizard-notification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "whizard-notification" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notification into .gemini/skills/whizard-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-notification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kubesphere/kubesphere whizard-notificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kubesphere/kubesphere --skill whizard-notification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/whizard-notification .github/skills/whizard-notification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "whizard-notification" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notification into .github/skills/whizard-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-notification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kubesphere/kubesphere --skill whizard-notification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kubesphere/kubesphere whizard-notification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubesphere/kubesphere.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/whizard-notification .opencode/skills/whizard-notification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "whizard-notification" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-notification into .opencode/skills/whizard-notification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-notification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
whizard-notification- GitHub stars
- 17k
- Token cost
- ~6.1k tokens
- SKILL.md length
- 864 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Installs and configures the WizTelemetry Notification extension for KubeSphere: channel setup, alert routing by tenant labels, silences and troubleshooting.
- Works in 2 steps: Get Latest Version (if not provided by… → Create InstallPlan
- Installing the WizTelemetry Notification extension on KubeSphere
- SKILL.md covers Overview, Architecture, Components and Dependencies, plus 4 more sections
- Calls kubectl and curl; reaches whizard-telemetry-apiserver.extension-whizard-telemetry.svc
What it does
WizTelemetry Notification is the component of the KubeSphere observability platform that receives alerts, cloud events and audit logs in a multi-tenant Kubernetes cluster and sends them to notification channels according to tenant labels such as namespace. This skill documents how it is built so the agent can install, configure and debug it.
It lists the pieces that make up the extension, including notification-manager, Alertmanager, an Alertmanager proxy and a notification history stored through Vector in OpenSearch, together with the extensions it depends on. It also covers the five custom resources in the notification.kubesphere.io group, namely NotificationManager, Receiver, Config, Router and Silence, and the 11 supported channels, with Email and Slack among them.
When your agent uses it
- Installing the WizTelemetry Notification extension on KubeSphere
- Setting up an email or Slack receiver for tenant alerts
- Routing alerts to different receivers based on label matchers
- Silencing alerts for a set time window or debugging missing notifications
Example prompts
- “Install WizTelemetry Notification on our host cluster with notification history turned on.”
- “Create a Slack receiver for the payments namespace and route its alerts to it.”
- “Add a silence for node maintenance that mutes alerts with the label env=staging.”
- “Alerts fire in Alertmanager but nobody gets an email, help me trace it.”
Requirements
- A KubeSphere installation with the whizard-telemetry extension
- kubectl access to the cluster
Workflow steps
2 steps, taken from the step headings in SKILL.md.
- Get Latest Version (if not provided by user)
- Create InstallPlan
What it can do on your machine
Read from SKILL.md and the folder at commit 04a29b5. 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:
kubectlcurl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
whizard-telemetry-apiserver.extension-whizard-telemetry.svc
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
WizTelemetry Notification loads about 6.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 864 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 864 words (~6,122 tokens).
“WizTelemetry Notification is the notification component of the KubeSphere observability platform. It receives alerts, cloud events, and audit logs in a multi-tenant Kubernetes environment and distributes notifications to different channels based on tenant labels (e.g., namespace).”
- name
- whizard-notification
Files
Just SKILL.md in skills/whizard-notification of kubesphere/kubesphere.
Open the folder on GitHubat commit 04a29b5
Compare with similar skills
WizTelemetry Notification 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| WizTelemetry Notification this skillkubesphere/kubesphere | 17k | — | ~6.1k | Automated safety check: Pass | Custom licence | |
| Alloygrafana/skills | 278 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Gke Observabilitygoogle/skills | 21k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Tsh Implementing ObservabilityTheSoftwareHouse/copilot-collections | 284 | — | ~2k | Automated safety check: Pass | MIT | |
| Kratos Developmentaide-family/moon | 253 | — | ~1.5k | Automated safety check: Pass | None | |
| Happy Infra Metrics and Grafanaslopus/happy | 24k | — | ~2k | Automated safety check: Notes | MIT |
Similar skills
- Official
- Official
Gke Observability
google/skills
Configures GKE observability, including Cloud Logging, Cloud Monitoring, and managed Prometheus.
Tsh Implementing Observability
TheSoftwareHouse/copilot-collections
Observability patterns for logging, monitoring, alerting, and distributed tracing.
Kratos Development
aide-family/moon
Develops Go microservices with Kratos v2 following official design philosophy, DDD/Clean Architecture layout, Protobuf API, error/config/middleware patterns, and observability.
Happy Infra Metrics and Grafana
slopus/happy
Queries live Prometheus metrics and manages Grafana dashboards as code for Happy's infrastructure, using the grafanactl CLI and the Grafana datasource proxy API.
- Official
Redis Observability
redis/agent-skills
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
More from kubesphere/kubesphere
All 32 skills in this repoKubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
KubeEye Cluster Inspection
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
KubeSphere NodeGroup Operations
kubesphere/kubesphere
Queries, creates, updates, binds and troubleshoots NodeGroup resources in the edgewize nodegroup project through a bundled authenticated API script.
WizTelemetry Platform Service
kubesphere/kubesphere
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
Frontend Forge Extension Operations
kubesphere/kubesphere
Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.
Related
Works with
Categories
Questions about WizTelemetry Notification
What does WizTelemetry Notification do?
Installs and configures the WizTelemetry Notification extension for KubeSphere: channel setup, alert routing by tenant labels, silences and troubleshooting. WizTelemetry Notification is the component of the KubeSphere observability platform that receives alerts, cloud events and audit logs in a multi-tenant Kubernetes cluster and sends them to notification channels according to tenant labels such as namespace. This skill documents how it is built so the agent can install, configure and debug it.
When should I use WizTelemetry Notification?
WizTelemetry Notification fits situations like: installing the WizTelemetry Notification extension on KubeSphere; setting up an email or Slack receiver for tenant alerts; routing alerts to different receivers based on label matchers; silencing alerts for a set time window or debugging missing notifications.
How do I install WizTelemetry Notification in Claude Code?
Run `npx skills add kubesphere/kubesphere --skill whizard-notification -a claude-code`. Or copy the skill folder (skills/whizard-notification in kubesphere/kubesphere) into .claude/skills/whizard-notification in your project. Claude Code loads it when a task matches its description.
How do I install WizTelemetry Notification in Codex?
Run `npx skills add kubesphere/kubesphere --skill whizard-notification -a codex`. Or copy the skill folder (skills/whizard-notification in kubesphere/kubesphere) into .agents/skills/whizard-notification in your project. Codex loads it when a task matches its description.
Can I use WizTelemetry Notification 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 kubesphere/kubesphere --skill whizard-notification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/whizard-notification, .gemini/skills/whizard-notification, .github/skills/whizard-notification and .opencode/skills/whizard-notification in your project.
What does WizTelemetry Notification need to run?
Going by SKILL.md and its folder, WizTelemetry Notification needs the command-line tools its instructions call (kubectl and curl). Our summary lists: A KubeSphere installation with the whizard-telemetry extension; kubectl access to the cluster.
Does WizTelemetry Notification access the network?
SKILL.md names 1 domain. In commands or code: whizard-telemetry-apiserver.extension-whizard-telemetry.svc; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is WizTelemetry Notification 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 WizTelemetry Notification use?
WizTelemetry Notification has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does WizTelemetry Notification use?
About 6.1k tokens (SKILL.md is roughly 24k 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 WizTelemetry Notification?
Skills that share tags, products or a category with WizTelemetry Notification: Alloy (grafana/skills, 278 stars), Gke Observability (google/skills, 21k stars), Tsh Implementing Observability (TheSoftwareHouse/copilot-collections, 284 stars) and Kratos Development (aide-family/moon, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains WizTelemetry Notification?
kubesphere (a GitHub organization) maintains it in kubesphere/kubesphere, which has 17,059 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on July 15, 2026.
Source: kubesphere/kubesphere on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.