Operate FrontendExtension (FE) resources in frontend-forge: create, update, rebuild, inspect package artifacts, download packages, publish, unpublish, delete, and debug package/publish controller behavior. Use this skill whenever the user mentions FE operations, FrontendExtension lifecycle, extension package/download/publish/unpublish, artifact ConfigMaps, package Jobs, publisher Jobs, publish target ConfigMaps or Secrets, rebuild-token, package-state/publish-state labels, or troubleshooting FE status in a Kubernetes cluster.
wiztelemetry-tracing
wiztelemetry-tracing is an open-source devops skill for Claude Code and compatible agents, published by kubesphere. Its author describes it as: “Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API”. The project has 17k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/kubesphere/kubesphere ~/.claude/skills/wiztelemetry-tracing`.
What wiztelemetry-tracing does
WizTelemetry Tracing is an extension component in the KubeSphere Observability Platform that provides distributed tracing functionality based on the OpenTelemetry standard.
Installation
Add wiztelemetry-tracing to your agent with:
git clone https://github.com/kubesphere/kubesphere ~/.claude/skills/wiztelemetry-tracing Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for wiztelemetry-tracing is organised into these sections:
- Overview
- When to Use
- Components
- Dependencies
- Installation
- Prerequisites
- Enable Agent (Log File Collection)
- Enable Demo
- Send Traces to Tempo
- Multiple Generator Instances
- Configuration Parameters
- Global Parameters
When to use it
Reach for wiztelemetry-tracing when you want devops help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Ships in kubesphere/kubesphere, an established project with 17,028 GitHub stars
- Actively maintained (recent commits)
Things to check
- No license declared — confirm terms with the author before reuse
Topics
Frequently asked questions
- What does wiztelemetry-tracing do?
- Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API
- How do I install wiztelemetry-tracing?
- Run git clone https://github.com/kubesphere/kubesphere ~/.claude/skills/wiztelemetry-tracing in your agent, then reload your skills. Review the source at https://github.com/kubesphere/kubesphere before installing.
- Is wiztelemetry-tracing free to use?
- wiztelemetry-tracing is publicly available on GitHub, but kubesphere has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
- Where does wiztelemetry-tracing come from?
- wiztelemetry-tracing ships inside kubesphere/kubesphere, a repository that contains 33 catalogued skills in total. The repository's 17,028 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More DevOps →Operate FrontendIntegration resources and the frontend-forge extension. Use when Codex needs to create a FrontendIntegration from FrontendIntegration YAML, update or patch FI lifecycle state, inspect or troubleshoot FI build output, or create, enable, disable, uninstall, and inspect the frontend-forge extension through its InstallPlan and extension resources.
Generate canonical FrontendIntegration YAML from a simplified single-menu authoring model for frontend-forge.
Use when deploying KubeEye for cluster inspection, creating InspectRule/InspectPlan resources, or retrieving inspection results. Covers InstallPlan-based deployment, OPA/PromQL/FileChange/Sysctl/Systemd/NodeInfo/FileFilter/ServiceConnect/CustomCommand rule types, and report retrieval. Always consult this skill when the user mentions KubeEye, cluster inspection, InspectRule, InspectPlan, or inspection reports.
KubeSphere cluster query Skill (read-only). Use when user requests to view cluster list, cluster status, cluster details, or cluster version info. Do not perform any write operations (create, delete, update). Use KubeSphere Console for management operations.