AGENT SKILL

kubestellar-console

Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills

License 许可
Apache-2.0
最近更新
2026-10-22
Stars
★ 1
Forks
0

01 前言 Front Matter

name
kubestellar-console
risk
critical
tags
[ "kubernetes", "multi-cluster", "mcp", "dashboard", "cncf", "devops", "observability" ]
tools
[ "claude", "cursor", "gemini", "codex" ]
author
kubestellar
plugin
{ "setup": { "docs": "https://github.com/kubestellar/console#quick-start", "type": "manual", "summary": "Requires kc-agent binary (brew tap kubestellar/tap && brew install kc-agent)" } }
source
community
license
Apache-2.0
category
devops
date_added
2026-04-27
description
Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills
source_repo
kubestellar/console
source_type
community
license_source
https://github.com/kubestellar/console/blob/main/LICENSE

03 SKILL.md 正文

KubeStellar Console

Overview

KubeStellar Console is an open-source multi-cluster Kubernetes dashboard (CNCF project) with AI-powered operations. It ships with kc-agent, an MCP server that bridges coding agents to kubeconfig and Kubernetes APIs, plus 10+ built-in agent skills for development, testing, and operations.

When to Use This Skill

  • Use when managing multiple Kubernetes clusters across edge and cloud
  • Use when you need AI-assisted Kubernetes troubleshooting and debugging
  • Use when running performance tests, cache compliance checks, or CI debugging on a Kubernetes dashboard
  • Use when integrating with CNCF projects (Argo, Kyverno, Istio, and 20+ others)

How It Works

Step 1: Install kc-agent

brew tap kubestellar/tap && brew install kc-agent

Step 2: Start the MCP server

kc-agent

This bridges the active kubeconfig context to any MCP-compatible coding agent. Do not start it from a cluster-admin or write-capable context unless the user explicitly accepts that risk.

Step 3: Use built-in agent skills

The project ships with agent skills accessible via CLAUDE.md and AGENTS.md:

  • @perf-test — Dashboard performance testing and TTFI analysis
  • @cache-test — Card cache compliance testing (IndexedDB warm return)
  • @nav-test — Navigation performance testing
  • @ui-compliance-test — Card loading compliance (8 criteria, 150+ cards)
  • @ci-status — CI pipeline monitoring and status checks
  • @rca — Root cause analysis for CI/test failures
  • @tdd — Test-driven development workflow
  • @k8s-debug — Kubernetes debugging and troubleshooting

Key Features

  • Multi-cluster management across edge and cloud
  • Real-time streaming observability
  • 20+ CNCF project integrations (Argo, Kyverno, Istio, etc.)
  • GitHub OAuth authentication
  • Supply chain security (SBOM, SLSA)
  • SQLite WASM caching with stale-while-revalidate pattern
  • 15+ themes with dark/light mode

Security & Safety Notes

  • Critical risk: kc-agent bridges your active kubeconfig context to MCP-compatible agents. If that context carries cluster-admin, write permissions, or secret read access, agents inherit those capabilities.
  • Do not rely on RBAC objects alone: creating a ServiceAccount or ClusterRoleBinding does not change the credentials kc-agent uses. Start kc-agent only after switching KUBECONFIG/context to dedicated least-privilege credentials and verifying them.
  • Recommended read-only scope: avoid resources='*', because it includes sensitive objects such as Secrets. Prefer an explicit non-secret resource list and verify access before starting the MCP server:
    kubectl create serviceaccount kc-agent -n default
    kubectl create clusterrole kc-agent-readonly \
      --verb=get,list,watch \
      --resource=pods,services,deployments.apps,replicasets.apps,statefulsets.apps,daemonsets.apps,namespaces,nodes,events,configmaps
    kubectl create clusterrolebinding kc-agent-readonly \
      --clusterrole=kc-agent-readonly \
      --serviceaccount=default:kc-agent
    kubectl auth can-i get secrets --as=system:serviceaccount:default:kc-agent
    kubectl auth can-i list pods --as=system:serviceaccount:default:kc-agent
    
  • The first can-i command must return no; the second should return yes. Then create or select a kubeconfig that actually authenticates as that ServiceAccount before running kc-agent.
  • Do not expose kc-agent on a public network without authentication.
  • Review SECURITY-AI.md for prompt injection and agent drift mitigations.

Limitations

  • This skill requires an external binary (kc-agent) installed separately via Homebrew.
  • Do not treat agent output as a substitute for environment-specific validation or expert review.
  • Stop and ask for clarification if required permissions or safety boundaries are unclear.

Links

04 同仓库更多 Skills

Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

infer-conventions

Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

inertia-react-development

Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

★ 1