Logfire Infrastructure
pydantic/skills
Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.
Installs and configures WizTelemetry Tracing for KubeSphere, an OpenTelemetry-based tracing extension, and covers its components, query API and auto-instrumentation.
Install KubeSphere WizTelemetry Tracing
$ npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kubesphere/kubesphere wiztelemetry-tracing --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/wiztelemetry-tracing .claude/skills/wiztelemetry-tracing && 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 "wiztelemetry-tracing" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/wiztelemetry-tracing into .claude/skills/wiztelemetry-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiztelemetry-tracing", 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/wiztelemetry-tracingType 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 wiztelemetry-tracing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kubesphere/kubesphere wiztelemetry-tracing --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/wiztelemetry-tracing .agents/skills/wiztelemetry-tracing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wiztelemetry-tracing" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/wiztelemetry-tracing into .agents/skills/wiztelemetry-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiztelemetry-tracing", 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 wiztelemetry-tracing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kubesphere/kubesphere wiztelemetry-tracing --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/wiztelemetry-tracing .cursor/skills/wiztelemetry-tracing && 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 "wiztelemetry-tracing" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/wiztelemetry-tracing into .cursor/skills/wiztelemetry-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiztelemetry-tracing", 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/wiztelemetry-tracing--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 wiztelemetry-tracing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kubesphere/kubesphere wiztelemetry-tracing --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/wiztelemetry-tracing .gemini/skills/wiztelemetry-tracing && 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 "wiztelemetry-tracing" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/wiztelemetry-tracing into .gemini/skills/wiztelemetry-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiztelemetry-tracing", 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 wiztelemetry-tracingInstalls 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 wiztelemetry-tracing -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/wiztelemetry-tracing .github/skills/wiztelemetry-tracing && 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 "wiztelemetry-tracing" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/wiztelemetry-tracing into .github/skills/wiztelemetry-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiztelemetry-tracing", 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 wiztelemetry-tracing -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 wiztelemetry-tracing --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/wiztelemetry-tracing .opencode/skills/wiztelemetry-tracing && 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 "wiztelemetry-tracing" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/wiztelemetry-tracing into .opencode/skills/wiztelemetry-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiztelemetry-tracing", 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
wiztelemetry-tracing- GitHub stars
- 17k
- Token cost
- ~4.6k tokens
- SKILL.md length
- 1,139 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Installs and configures WizTelemetry Tracing for KubeSphere, an OpenTelemetry-based tracing extension, and covers its components, query API and auto-instrumentation.
- Works in 5 steps: Get Available Clusters and Confirm Target → Get Latest Version (if not provided by… → Get Generator Endpoint → …
- Installing distributed tracing on a KubeSphere cluster
- SKILL.md covers Overview, When to Use, Components and Dependencies, plus 4 more sections
- Calls kubectl and curl; reaches whizard-telemetry-apiserver.extension-whizard-telemetry.svc and opensearch-cluster-data.kubesphere-logging-system.svc; needs OPENSEARCH_PASSWORD
What it does
This skill covers the WizTelemetry Tracing extension, which adds distributed tracing to the KubeSphere Observability Platform on the OpenTelemetry standard. It is built from a generator, an operator, a collector and an optional agent: the generator builds service graphs from trace data, the operator manages the OpenTelemetry Collector and auto-instrumentation, the collector receives traces and exports them to Vector and OpenSearch, and the agent reads trace data from local log files. A demo component can produce sample traces. Only the generator, operator and collector are on by default.
Dependencies are the WizTelemetry Platform Service and OpenSearch. The install sequence has the agent list clusters and confirm targets, query the latest extension version in the `kubesphere-system` namespace, then obtain a generator endpoint. Beyond installation, the skill covers the tracing query API for traces, spans and service graphs and configuring OpenTelemetry auto-instrumentation for applications. The text available here ends at the generator endpoint step.
When your agent uses it
- Installing distributed tracing on a KubeSphere cluster
- Querying traces, spans or service graphs through the tracing API
- Setting up OpenTelemetry auto-instrumentation for an application
- Generating sample tracing data to try out the extension
Example prompts
- “Install WizTelemetry Tracing on the host and dev clusters.”
- “Show me the service graph for the checkout service using the tracing API.”
- “How do I turn on OpenTelemetry auto-instrumentation for the deployments in the shop namespace?”
- “Enable the demo component so we can see sample traces.”
Requirements
- The WizTelemetry Platform Service and OpenSearch extensions
- kubectl access to a KubeSphere cluster
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Get Available Clusters and Confirm Target
- Get Latest Version (if not provided by user)
- Get Generator Endpoint
- Confirm Configuration with 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.svcopensearch-cluster-data.kubesphere-logging-system.svc
Also links to:
opentelemetry.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
OPENSEARCH_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
KubeSphere WizTelemetry Tracing loads about 4.6k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 1,139 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 1,139 words (~4,578 tokens).
“WizTelemetry Tracing is an extension component in the KubeSphere Observability Platform that provides distributed tracing functionality based on the OpenTelemetry standard.”
- name
- wiztelemetry-tracing
Files
Just SKILL.md in skills/wiztelemetry-tracing of kubesphere/kubesphere.
Open the folder on GitHubat commit 04a29b5
Compare with similar skills
KubeSphere WizTelemetry Tracing 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 |
|---|---|---|---|---|---|---|
| KubeSphere WizTelemetry Tracing this skillkubesphere/kubesphere | 17k | — | ~4.6k | Automated safety check: Pass | Custom licence | |
| Logfire Infrastructurepydantic/skills | 140 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Error HandlerEliasOulkadi/shokunin | 114 | — | ~3.6k | Automated safety check: Notes | MIT | |
| Alloygrafana/skills | 281 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Observability K8s Investigationelastic/agent-skills | 592 | — | ~8.3k | Automated safety check: Pass | Apache-2.0 | |
| Sap Btp Cloud Loggingsecondsky/sap-skills | 462 | — | ~4k | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
Error Handler
EliasOulkadi/shokunin
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…
- Official
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 /…
- Official
Observability K8s Investigation
elastic/agent-skills
Investigate Kubernetes workload, node, and control-plane issues using OTel telemetry (EDOT).
Sap Btp Cloud Logging
secondsky/sap-skills
This skill provides comprehensive guidance for SAP Cloud Logging service on SAP BTP.
- Official
Opentelemetry
grafana/skills
Instrument any app with OpenTelemetry and ship metrics / logs / traces to Grafana Cloud or self-hosted Mimir / Loki / Tempo / Pyroscope.
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 KubeSphere WizTelemetry Tracing
What does KubeSphere WizTelemetry Tracing do?
Installs and configures WizTelemetry Tracing for KubeSphere, an OpenTelemetry-based tracing extension, and covers its components, query API and auto-instrumentation. This skill covers the WizTelemetry Tracing extension, which adds distributed tracing to the KubeSphere Observability Platform on the OpenTelemetry standard. It is built from a generator, an operator, a collector and an optional agent: the generator builds service graphs from trace data, the operator manages the OpenTelemetry Collector and auto-instrumentation, the collector receives traces and exports them to Vector and OpenSearch, and the agent reads trace data from local log files.
When should I use KubeSphere WizTelemetry Tracing?
KubeSphere WizTelemetry Tracing fits situations like: installing distributed tracing on a KubeSphere cluster; querying traces, spans or service graphs through the tracing API; setting up OpenTelemetry auto-instrumentation for an application; generating sample tracing data to try out the extension.
How do I install KubeSphere WizTelemetry Tracing in Claude Code?
Run `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a claude-code`. Or copy the skill folder (skills/wiztelemetry-tracing in kubesphere/kubesphere) into .claude/skills/wiztelemetry-tracing in your project. Claude Code loads it when a task matches its description.
How do I install KubeSphere WizTelemetry Tracing in Codex?
Run `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a codex`. Or copy the skill folder (skills/wiztelemetry-tracing in kubesphere/kubesphere) into .agents/skills/wiztelemetry-tracing in your project. Codex loads it when a task matches its description.
Can I use KubeSphere WizTelemetry Tracing 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 wiztelemetry-tracing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wiztelemetry-tracing, .gemini/skills/wiztelemetry-tracing, .github/skills/wiztelemetry-tracing and .opencode/skills/wiztelemetry-tracing in your project.
What does KubeSphere WizTelemetry Tracing need to run?
Going by SKILL.md and its folder, KubeSphere WizTelemetry Tracing needs the command-line tools its instructions call (kubectl and curl) and credentials named OPENSEARCH_PASSWORD. Our summary lists: The WizTelemetry Platform Service and OpenSearch extensions; kubectl access to a KubeSphere cluster.
Does KubeSphere WizTelemetry Tracing access the network?
SKILL.md names 3 domains. In commands or code: whizard-telemetry-apiserver.extension-whizard-telemetry.svc and opensearch-cluster-data.kubesphere-logging-system.svc; the agent is likely to contact these when it follows the instructions. As links in the text: opentelemetry.io. This is read from the text; nothing was executed.
Is KubeSphere WizTelemetry Tracing 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 KubeSphere WizTelemetry Tracing use?
KubeSphere WizTelemetry Tracing 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 KubeSphere WizTelemetry Tracing use?
About 4.6k tokens (SKILL.md is roughly 18k 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 KubeSphere WizTelemetry Tracing?
Skills that share tags, products or a category with KubeSphere WizTelemetry Tracing: Logfire Infrastructure (pydantic/skills, 140 stars), Error Handler (EliasOulkadi/shokunin, 114 stars), Alloy (grafana/skills, 281 stars) and Observability K8s Investigation (elastic/agent-skills, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains KubeSphere WizTelemetry Tracing?
kubesphere (a GitHub organization) maintains it in kubesphere/kubesphere, which has 17,057 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.