New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Karmada Dashboard Quickstart

by karmada-io in karmada-io/dashboard

QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access.

Apache-2.0Auto-check passedDevOps & Cloud

Install Karmada Dashboard Quickstart

skills CLI
$ npx skills add karmada-io/dashboard --skill karmada-dashboard-quickstart -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install karmada-io/dashboard karmada-dashboard-quickstart --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/karmada-io/dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/karmada-dashboard-quickstart .claude/skills/karmada-dashboard-quickstart && rm -rf skills-src

Use ~/.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/

Facts

Skill name
karmada-dashboard-quickstart
GitHub stars
105
Token cost
~1.4k tokens
SKILL.md length
439 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access.

  • Works in 5 steps: Create the kubeconfig secret → Deploy the dashboard (NodePort overlay) → Create the login ServiceAccount and get… → …
  • Asked to bring up / install / start the dashboard following the README QuickStart
  • SKILL.md covers Assumptions / prerequisites, Step 1 — Create the kubeconfig…, Step 2 — Deploy the dashboard… and Step 3 — Create the login…, plus 3 more sections
  • Calls kubectl, bash and curl

What it does

Karmada Dashboard Quickstart is an agent skill from karmada-io/dashboard. QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access. Use when asked to bring up / install / start the dashboard following the README QuickStart, especially on a kind cluster or a cloud VM (e.g. Oracle Cloud) where the dashboard must be reachable from another host.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Frontend development and Technical documentation. It works with Kubernetes. The licence is Apache-2.0.

When your agent uses it

  • Asked to bring up / install / start the dashboard following the README QuickStart
  • Especially on a kind cluster
  • A cloud VM (e.g

Example prompts

  • “/karmada-dashboard-quickstart”

Requirements

  • Docker

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Create the kubeconfig secret
  2. Deploy the dashboard (NodePort overlay)
  3. Create the login ServiceAccount and get the JWT token
  4. Expose the web UI on the host's 8000 port
  5. Accessing from another host (cloud VMs)

What it can do on your machine

Read from SKILL.md and the folder at commit c48e19e. 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:

    • kubectl
    • bash
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use kubectl and curl, 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

Karmada Dashboard Quickstart loads about 1.4k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 439 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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

The full file from karmada-io/dashboard at commit c48e19e, republished under its Apache-2.0 licence (© karmada-io). 439 words, ~1,379 tokens.

Download SKILL.mdSave it as .claude/skills/karmada-dashboard-quickstart/SKILL.md (or your agent's skills folder).
name
karmada-dashboard-quickstart
description
QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access. Use when asked to bring up / install / start the dashboard following the README QuickStart, especially on a kind cluster or a cloud VM (e.g. Oracle Cloud) where the dashboard must be reachable from another host.

Deploy Karmada Dashboard (kind dev env)

Brings up karmada-dashboard-api + karmada-dashboard-web (+ kubernetes-dashboard-api) on the karmada-host cluster and exposes the web UI on the host's 8000 port.

This skill encodes the working procedure and the non-obvious gotchas that the README QuickStart misses. Follow it top to bottom; skip steps only after verifying their state.

Assumptions / prerequisites

  • A Karmada control plane is already running (here: a kind dev env with clusters karmada-host, member1/2/3). Verify before doing anything:
    bash
    export KUBECONFIG="$HOME/.kube/karmada.config"
kubectl config use-context karmada-host
kubectl get deployments.apps -n karmada-system   # karmada-apiserver et al should be READY
  • Certs exist in $HOME/.karmada (ca.crt, ca.key, ca-config.json).
  • Tools available: kubectl, docker. Run all commands from the repo root.
  • The node can reach Docker Hub — the dashboard images (karmada/karmada-dashboard-*, karmada/kubernetes-dashboard-api, all imagePullPolicy: IfNotPresent) are pulled automatically on deploy. No manual image build/load is needed.
  • Two contexts exist in ~/.kube/karmada.config: karmada-host (where the dashboard runs) and karmada-apiserver (where the login ServiceAccount/token lives). Do not mix them up — this is a common source of errors.

Step 1 — Create the kubeconfig secret

The deployment manifests mount a secret named karmada-dashboard-config (see secretName: karmada-dashboard-config in artifacts/dashboard/karmada-dashboard-{web,api}.yaml). Create it with the helper script (it generates the dashboard client cert on demand from the CA in $HOME/.karmada):

bash
export KUBECONFIG="$HOME/.kube/karmada.config"
bash hack/generate-karmada-dashboard-kubeconfig.sh "$HOME/.kube/karmada.config" karmada-host
# -> creates secret/karmada-dashboard-config in namespace karmada-system

GOTCHA: the secret name must be exactly karmada-dashboard-config. Creating a plain kubeconfig secret instead (an older README instruction, now fixed) leaves the pods stuck in ContainerCreating with MountVolume.SetUp failed ... secret "karmada-dashboard-config" not found.

Step 2 — Deploy the dashboard (NodePort overlay)

Images are pulled automatically by the node.

bash
export KUBECONFIG="$HOME/.kube/karmada.config"
kubectl config use-context karmada-host
kubectl apply -k artifacts/overlays/nodeport-mode

Wait for rollout (first run also pulls images, so allow time):

bash
for d in karmada-dashboard-web karmada-dashboard-api kubernetes-dashboard-api; do
  kubectl rollout status deployment/$d -n karmada-system --timeout=180s
done
kubectl get pods -n karmada-system | grep -i dashboard   # all should be 1/1 Running
Show full SKILL.md (197 more words)Show less

Step 3 — Create the login ServiceAccount and get the JWT token

Switch context to karmada-apiserver for these (the SA/token live on the Karmada API server, not the host cluster):

bash
export KUBECONFIG="$HOME/.kube/karmada.config"
kubectl config use-context karmada-apiserver
kubectl apply -f artifacts/dashboard/karmada-dashboard-sa.yaml
# optional: member-cluster proxy access for cluster management
kubectl apply -f artifacts/dashboard/karmada-dashboard-clusterrolebinding.yaml

# fetch the token (paste into the dashboard "Enter token" field)
kubectl -n karmada-system get secret/karmada-dashboard-secret \
  -o go-template="{{.data.token | base64decode}}"

Step 4 — Expose the web UI on the host's 8000 port

GOTCHA: On kind, the NodePort (32000) only lives on the node container's internal IP, so it is not reachable from the host network. Use kubectl port-forward to publish the web service on the host's 8000 port (the README's documented alternative). Bind --address 0.0.0.0 so it listens on all interfaces (needed for remote access; use the default 127.0.0.1 if local-only is enough):

bash
export KUBECONFIG="$HOME/.kube/karmada.config"
kubectl config use-context karmada-host
kubectl port-forward -n karmada-system services/karmada-dashboard-web \
  --address 0.0.0.0 8000:8000
# run in background (nohup ... &) if it must outlive the shell

This process is session-bound: it dies if the shell exits, the host reboots, or the web pod restarts. For a durable setup, run it as a systemd service instead.

Verify locally: curl -s -o /dev/null -w "%{http_code}\n" http://127.0.0.1:8000/ → 200.

Step 5 — Accessing from another host (cloud VMs)

Step 4 already confirms local access works. To reach the dashboard from another machine when it runs on a public-cloud VM, remind the user to open the corresponding security group / firewall rule (e.g. an ingress rule for TCP port 8000) so inbound traffic can reach the host.

Quick teardown

bash
export KUBECONFIG="$HOME/.kube/karmada.config"
kubectl config use-context karmada-host
kubectl delete -k artifacts/overlays/nodeport-mode
kubectl -n karmada-system delete secret karmada-dashboard-config
# kill any running port-forward: pkill -f "port-forward.*karmada-dashboard-web"

© karmada-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/karmada-dashboard-quickstart of karmada-io/dashboard.

Open the folder on GitHubat commit c48e19e

Compare with similar skills

Karmada Dashboard Quickstart 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.

Karmada Dashboard Quickstart compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Karmada Dashboard Quickstart this skillkarmada-io/dashboard105—~1.4kAutomated safety check: PassApache-2.0
Draw.io Diagram StudioAgents365-ai/drawio-skill10k—~2.4kAutomated safety check: NotesMIT
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress5.1k—~1.4kAutomated safety check: PassApache-2.0
Borg Live Debugkaranhudia/borg-ui1.7k—~1.4kAutomated safety check: NotesAGPL-3.0
.NET Crash Dump Collectiondotnet/skills5.6k2 repos~1.1kAutomated safety check: PassMIT
Kurtosis Ethereumethpandaops/ethereum-package481—~1.6kAutomated safety check: NotesMIT

Similar skills

  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 7 days ago
    DevelopmentAuto-check: notes

  • NGINX Ingress Controller Feature Checklists

    nginx/kubernetes-ingress

    Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.

    5.1k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Borg Live Debug

    karanhudia/borg-ui

    Live Borg debugging by exec-ing into the borg-web-ui Docker container.

    1.7k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • .NET Crash Dump Collection

    dotnet/skills

    Official

    Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.

    5.6k GitHub starsUsed in 2 repos~1.1k tokens
    DevOps & CloudAuto-check passed

  • Kurtosis Ethereum

    ethpandaops/ethereum-package

    Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package.

    481 GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Provider Bug Review

    mondoohq/mql

    Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

    412 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed

Works with

Categories

Questions about Karmada Dashboard Quickstart

What does Karmada Dashboard Quickstart do?

QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access. Karmada Dashboard Quickstart is an agent skill from karmada-io/dashboard. QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access.

When should I use Karmada Dashboard Quickstart?

Karmada Dashboard Quickstart fits situations like: asked to bring up / install / start the dashboard following the README QuickStart; especially on a kind cluster; A cloud VM (e.g.

How do I install Karmada Dashboard Quickstart in Claude Code?

Run `npx skills add karmada-io/dashboard --skill karmada-dashboard-quickstart -a claude-code`. Or copy the skill folder (.claude/skills/karmada-dashboard-quickstart in karmada-io/dashboard) into .claude/skills/karmada-dashboard-quickstart in your project. Claude Code loads it when a task matches its description.

How do I install Karmada Dashboard Quickstart in Codex?

Run `npx skills add karmada-io/dashboard --skill karmada-dashboard-quickstart -a codex`. Or copy the skill folder (.claude/skills/karmada-dashboard-quickstart in karmada-io/dashboard) into .agents/skills/karmada-dashboard-quickstart in your project. Codex loads it when a task matches its description.

Can I use Karmada Dashboard Quickstart 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 karmada-io/dashboard --skill karmada-dashboard-quickstart -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/karmada-dashboard-quickstart, .gemini/skills/karmada-dashboard-quickstart, .github/skills/karmada-dashboard-quickstart and .opencode/skills/karmada-dashboard-quickstart in your project.

What does Karmada Dashboard Quickstart need to run?

Going by SKILL.md and its folder, Karmada Dashboard Quickstart needs the command-line tools its instructions call (kubectl, bash and curl). Our summary lists: Docker.

Does Karmada Dashboard Quickstart access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Karmada Dashboard Quickstart 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 Karmada Dashboard Quickstart use?

Karmada Dashboard Quickstart is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Karmada Dashboard Quickstart use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Karmada Dashboard Quickstart?

Skills that share tags, products or a category with Karmada Dashboard Quickstart: Draw.io Diagram Studio (Agents365-ai/drawio-skill, 10k stars), NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars), Borg Live Debug (karanhudia/borg-ui, 1.7k stars) and .NET Crash Dump Collection (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Karmada Dashboard Quickstart?

karmada-io (a GitHub organization) maintains it in karmada-io/dashboard, which has 105 GitHub stars. The repository was last updated on October 8, 2026.

Source: karmada-io/dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.