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 Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
Install WizTelemetry Platform Service
$ npx skills add kubesphere/kubesphere --skill whizard-telemetry -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry --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-telemetry .claude/skills/whizard-telemetry && 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-telemetry" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry into .claude/skills/whizard-telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry", 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-telemetryType 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-telemetry -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry --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-telemetry .agents/skills/whizard-telemetry && 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-telemetry" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry into .agents/skills/whizard-telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry", 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-telemetry -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry --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-telemetry .cursor/skills/whizard-telemetry && 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-telemetry" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry into .cursor/skills/whizard-telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry", 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-telemetry--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-telemetry -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry --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-telemetry .gemini/skills/whizard-telemetry && 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-telemetry" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry into .gemini/skills/whizard-telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry", 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-telemetryInstalls 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-telemetry -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-telemetry .github/skills/whizard-telemetry && 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-telemetry" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry into .github/skills/whizard-telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry", 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-telemetry -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-telemetry --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-telemetry .opencode/skills/whizard-telemetry && 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-telemetry" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry into .opencode/skills/whizard-telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry", 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-telemetry- GitHub stars
- 17k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 476 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
- Works in 3 steps: Check which observability extensions are… → Check if vector extension is installed → Output the config section only (between…
- Installing the WizTelemetry Platform Service extension on KubeSphere
- SKILL.md covers Overview, When to Use, Architecture and Installation, plus 3 more sections
- Runs Shell scripts from its folder; calls kubectl
What it does
WizTelemetry Platform Service provides a common APIServer and web console for KubeSphere's observability extensions, offering backend services for logging, auditing, events, notifications and tracing. It has no hard dependencies: OpenSearch is needed only for logging, auditing, events, notification history or traffic APIs, Prometheus for monitoring, Notification Manager for notifications and Whizard for global observability.
Installation starts by finding the latest extension version with kubectl, then running scripts/generate-config.sh, which checks which Whizard extensions and the vector extension are installed and prints only the config section between its markers. That output goes into a KubeSphere InstallPlan. Configuration is meant to grow as you deploy more observability extensions such as logging, auditing, events and notification.
When your agent uses it
- Installing the WizTelemetry Platform Service extension on KubeSphere
- Configuring OpenSearch connections for observability data types
- Enabling global observability monitoring
Example prompts
- “Install the WizTelemetry Platform Service on my KubeSphere cluster with the right config for what is already installed.”
- “Which WizTelemetry components need OpenSearch and which need Prometheus?”
Requirements
- A KubeSphere cluster with kubectl access
- OpenSearch, Prometheus or Notification Manager, depending on which APIs you enable
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Check which observability extensions are installed (whizard-logging, whizard-auditing, whizard-events, whizard-notification…
- Check if vector extension is installed
- Output the config section only (between ---CONFIG_START--- and ---CONFIG_END---)
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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
kubectl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use kubectl, which can reach the network depending on how they are called.
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 Platform Service loads about 1.8k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 476 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); the scripts in this folder 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 476 words (~1,759 tokens).
“WizTelemetry Platform Service is a common service for all observability extensions of KubeSphere's WizTelemetry Observability Platform. It provides a common APIServer for all observability extensions, offering backend platform services for Logging, Auditing, Events, Notifications, Tracing, and more.”
- name
- whizard-telemetry
Files
SKILL.md and 1 other file (scripts) in skills/whizard-telemetry of kubesphere/kubesphere.
- SKILL.md
- scripts/generate-config.sh
Open the folder on GitHubat commit 04a29b5
Compare with similar skills
WizTelemetry Platform Service 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 Platform Service this skillkubesphere/kubesphere | 17k | — | ~1.8k | 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.
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.
Frontend Forge FI Operations
kubesphere/kubesphere
Operates FrontendIntegration resources and the frontend-forge extension with kubectl: create from YAML, update, enable, disable, delete, inspect and troubleshoot builds.
Related
Works with
Categories
Questions about WizTelemetry Platform Service
What does WizTelemetry Platform Service do?
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions. WizTelemetry Platform Service provides a common APIServer and web console for KubeSphere's observability extensions, offering backend services for logging, auditing, events, notifications and tracing. It has no hard dependencies: OpenSearch is needed only for logging, auditing, events, notification history or traffic APIs, Prometheus for monitoring, Notification Manager for notifications and Whizard for global observability.
When should I use WizTelemetry Platform Service?
WizTelemetry Platform Service fits situations like: installing the WizTelemetry Platform Service extension on KubeSphere; configuring OpenSearch connections for observability data types; enabling global observability monitoring.
How do I install WizTelemetry Platform Service in Claude Code?
Run `npx skills add kubesphere/kubesphere --skill whizard-telemetry -a claude-code`. Or copy the skill folder (skills/whizard-telemetry in kubesphere/kubesphere) into .claude/skills/whizard-telemetry in your project. Claude Code loads it when a task matches its description.
How do I install WizTelemetry Platform Service in Codex?
Run `npx skills add kubesphere/kubesphere --skill whizard-telemetry -a codex`. Or copy the skill folder (skills/whizard-telemetry in kubesphere/kubesphere) into .agents/skills/whizard-telemetry in your project. Codex loads it when a task matches its description.
Can I use WizTelemetry Platform Service 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-telemetry -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-telemetry, .gemini/skills/whizard-telemetry, .github/skills/whizard-telemetry and .opencode/skills/whizard-telemetry in your project.
What does WizTelemetry Platform Service need to run?
Going by SKILL.md and its folder, WizTelemetry Platform Service needs a shell for the scripts in its folder and the command-line tools its instructions call (kubectl). Our summary lists: A KubeSphere cluster with kubectl access; OpenSearch, Prometheus or Notification Manager, depending on which APIs you enable.
Does WizTelemetry Platform Service 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 WizTelemetry Platform Service 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does WizTelemetry Platform Service use?
WizTelemetry Platform Service 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 Platform Service use?
About 1.8k tokens (SKILL.md is roughly 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 WizTelemetry Platform Service?
Skills that share tags, products or a category with WizTelemetry Platform Service: 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 Platform Service?
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.