clidash CLI Dashboard for NanoClaw
nanocoai/nanoclaw
Installs clidash, a dependency-free web dashboard that turns the JSON resource listings of a CLI such as NanoClaw's ncl into read-only tabs and tables.
Installs the WizTelemetry Ruler extension for KubeSphere and manages event, audit and log alerting rules as RuleGroup and ClusterRuleGroup resources.
Install WizTelemetry Ruler
$ npx skills add kubesphere/kubesphere --skill whizard-telemetry-ruler -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry-ruler --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-ruler .claude/skills/whizard-telemetry-ruler && 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-ruler" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry-ruler into .claude/skills/whizard-telemetry-ruler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry-ruler", 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-telemetry-rulerType 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-ruler -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry-ruler --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-ruler .agents/skills/whizard-telemetry-ruler && 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-ruler" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry-ruler into .agents/skills/whizard-telemetry-ruler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry-ruler", 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-ruler -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry-ruler --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-ruler .cursor/skills/whizard-telemetry-ruler && 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-ruler" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry-ruler into .cursor/skills/whizard-telemetry-ruler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry-ruler", 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-ruler--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-ruler -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kubesphere/kubesphere whizard-telemetry-ruler --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-ruler .gemini/skills/whizard-telemetry-ruler && 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-ruler" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry-ruler into .gemini/skills/whizard-telemetry-ruler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry-ruler", 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-telemetry-rulerInstalls 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-ruler -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-ruler .github/skills/whizard-telemetry-ruler && 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-ruler" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry-ruler into .github/skills/whizard-telemetry-ruler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry-ruler", 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-ruler -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-ruler --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-ruler .opencode/skills/whizard-telemetry-ruler && 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-ruler" agent skill from https://github.com/kubesphere/kubesphere/tree/master/skills/whizard-telemetry-ruler into .opencode/skills/whizard-telemetry-ruler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whizard-telemetry-ruler", 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-ruler- GitHub stars
- 17k
- Token cost
- ~6.5k tokens
- SKILL.md length
- 1,473 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Installs the WizTelemetry Ruler extension for KubeSphere and manages event, audit and log alerting rules as RuleGroup and ClusterRuleGroup resources.
- Works in 3 steps: Get Available Clusters and Confirm Target → Get Latest Version (if not provided by… → Get AlertManager Host (if configuring…
- Installing the WizTelemetry Ruler extension on selected KubeSphere clusters
- SKILL.md covers Overview, When to Use, Components and Dependencies, plus 4 more sections
- Calls curl and kubectl; reaches whizard-telemetry-apiserver.extension-whizard-telemetry.svc
What it does
WizTelemetry Ruler adds event alerting and log alerting to the KubeSphere observability platform. It evaluates Kubernetes events, KubeSphere audit events and Kubernetes logs against alerting rules and forwards matching alerts to receivers such as Alertmanager. The skill helps the agent install and configure the extension and create, update or delete rules as RuleGroup or ClusterRuleGroup resources.
Installation follows an ordered checklist. The agent lists the available clusters with kubectl and confirms which ones to deploy to, asking you when you have not said, then looks up the latest extension version from the cluster before it generates an InstallPlan. The skill also lists dependencies: whizard-telemetry is required, while events, auditing, logging, the data pipeline and OpenSearch are needed only for the matching alerting or persistence features.
When your agent uses it
- Installing the WizTelemetry Ruler extension on selected KubeSphere clusters
- Writing alerting rules for Kubernetes events or audit events
- Creating log-based alerting rules with a RuleGroup
- Updating or deleting existing alerting rules through the ruler API
Example prompts
- “Install WizTelemetry Ruler on the host and dev clusters.”
- “Add a ClusterRuleGroup that alerts when a Pod is evicted.”
- “Create a log alert rule that fires on repeated ERROR lines in the payments namespace.”
- “Delete the old audit alert rule group named privileged-exec.”
Requirements
- A KubeSphere installation with the whizard-telemetry extension
- kubectl access to the cluster
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Get Available Clusters and Confirm Target
- Get Latest Version (if not provided by user)
- Get AlertManager Host (if configuring sink)
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:
curlkubectl
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 Ruler loads about 6.5k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 1,473 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,473 words (~6,497 tokens).
“WizTelemetry Ruler is an extension component in the KubeSphere Observability Platform that provides event alerting and log alerting capabilities. It can define alerting rules for K8s native events, K8s/KubeSphere auditing events, and K8s logs, evaluate incoming event data and log…”
- name
- whizard-telemetry-ruler
Files
Just SKILL.md in skills/whizard-telemetry-ruler of kubesphere/kubesphere.
Open the folder on GitHubat commit 04a29b5
Compare with similar skills
WizTelemetry Ruler 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 Ruler this skillkubesphere/kubesphere | 17k | — | ~6.5k | Automated safety check: Pass | Custom licence | |
| clidash CLI Dashboard for NanoClawnanocoai/nanoclaw | 31k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Cloud Devopsdavila7/claude-code-templates | 32k | 4 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Alloygrafana/skills | 281 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Implementing Runtime Security With Tetragonmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.1k | Automated safety check: Notes | Apache-2.0 | |
| Loki Loggingsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Cloud Devops
davila7/claude-code-templates
Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.
- 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 /…
Implementing Runtime Security With Tetragon
mukul975/Anthropic-Cybersecurity-Skills
Implements eBPF-based runtime observability and in-kernel enforcement in Kubernetes with Cilium Tetragon, monitoring process execution, file access, network connections, and syscalls, and blocking…
Loki Logging
sickn33/agentic-awesome-skills
Configure Grafana Loki for log aggregation and analysis. An agent skill from sickn33/agentic-awesome-skills.
- Official
Observability Sre Triage
elastic/agent-skills
Triage a degraded or suspect service end to end: read SLO status and burn rate, check active alerting rules and ML anomalies, measure throughput, latency, and error rate, assess dependency health…
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 Ruler
What does WizTelemetry Ruler do?
Installs the WizTelemetry Ruler extension for KubeSphere and manages event, audit and log alerting rules as RuleGroup and ClusterRuleGroup resources. WizTelemetry Ruler adds event alerting and log alerting to the KubeSphere observability platform. It evaluates Kubernetes events, KubeSphere audit events and Kubernetes logs against alerting rules and forwards matching alerts to receivers such as Alertmanager.
When should I use WizTelemetry Ruler?
WizTelemetry Ruler fits situations like: installing the WizTelemetry Ruler extension on selected KubeSphere clusters; writing alerting rules for Kubernetes events or audit events; creating log-based alerting rules with a RuleGroup; updating or deleting existing alerting rules through the ruler API.
How do I install WizTelemetry Ruler in Claude Code?
Run `npx skills add kubesphere/kubesphere --skill whizard-telemetry-ruler -a claude-code`. Or copy the skill folder (skills/whizard-telemetry-ruler in kubesphere/kubesphere) into .claude/skills/whizard-telemetry-ruler in your project. Claude Code loads it when a task matches its description.
How do I install WizTelemetry Ruler in Codex?
Run `npx skills add kubesphere/kubesphere --skill whizard-telemetry-ruler -a codex`. Or copy the skill folder (skills/whizard-telemetry-ruler in kubesphere/kubesphere) into .agents/skills/whizard-telemetry-ruler in your project. Codex loads it when a task matches its description.
Can I use WizTelemetry Ruler 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-ruler -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-ruler, .gemini/skills/whizard-telemetry-ruler, .github/skills/whizard-telemetry-ruler and .opencode/skills/whizard-telemetry-ruler in your project.
What does WizTelemetry Ruler need to run?
Going by SKILL.md and its folder, WizTelemetry Ruler needs the command-line tools its instructions call (curl and kubectl). Our summary lists: A KubeSphere installation with the whizard-telemetry extension; kubectl access to the cluster.
Does WizTelemetry Ruler 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 Ruler 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 Ruler use?
WizTelemetry Ruler 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 Ruler use?
About 6.5k tokens (SKILL.md is roughly 26k 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 Ruler?
Skills that share tags, products or a category with WizTelemetry Ruler: clidash CLI Dashboard for NanoClaw (nanocoai/nanoclaw, 31k stars), Cloud Devops (davila7/claude-code-templates, 32k stars), Alloy (grafana/skills, 281 stars) and Implementing Runtime Security With Tetragon (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains WizTelemetry Ruler?
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.