Wiztelemetry Tracing
94TrustedInstructions onlyDistributed tracing setup and query API guidance for the KubeSphere platform.
What it does
WizTelemetry Tracing equips the assistant with domain-specific knowledge to manage the lifecycle of observability components within KubeSphere. It bridges the gap between high-level operational requirements and the technical specifics of OpenTelemetry integration, allowing the assistant to navigate complex cluster environments reliably.
By incorporating this skill, the assistant handles the intricate dependencies and configuration patterns required to deploy tracing services. It focuses on the accurate orchestration of telemetry agents and collectors, ensuring the underlying architecture aligns with the platform's requirements for distributed data ingestion and visualization.
When it earns its place
Reach for it when…
Use this skill when deploying or managing WizTelemetry Tracing within a KubeSphere cluster, particularly for determining current versions, mapping component dependencies like OpenSearch, or generating the necessary configuration structures for installation plans.
Look elsewhere when…
Do not use this for general troubleshooting of existing application code or custom instrumentations that do not rely on the KubeSphere-specific extension framework, as this tool is focused on infrastructure-level deployment and platform connectivity.
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 Tracing in my KubeSphere cluster?
- Show me the latest version of the WizTelemetry tracing extension.
- Help me configure an install plan for KubeSphere observability.
- What are the steps to connect my app to the tracing collector?
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.
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/wiztelemetry-tracing ~/.claude/skills/wiztelemetry-tracingInstall 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.
cp -r /tmp/kubesphere/skills/wiztelemetry-tracing .claude/skills/wiztelemetry-tracingIf 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
Wiztelemetry Tracing changes how the work is done. These servers change what Claude can reach while doing it.
- AWS Labs MCP Server76The skill encodes how your deployments are supposed to go; AWS Labs MCP Server is what lets Claude see the infrastructure they go to.
- Sentry MCP Server81Sentry MCP Server shows what actually broke, which is what turns a runbook from a document into a response.
- Circleci MCP Server58Pair with Circleci MCP Server so pipeline state informs the procedure rather than being described after the fact.