用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/phoroth/AGENTIC --skill kubestellar-console命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Development skill from AGENTIC (https://github.com/phoroth/AGENTIC)
Development skill from AGENTIC (https://github.com/phoroth/AGENTIC)
Generate clean, human-sounding, SEO-optimized WordPress blog posts with optional Yoast metadata, JSON-LD schema markup, and image SEO planning. Supports modular batch output.
基于 SOC 职业分类
正在显示 SKILL.md
| name | kubestellar-console |
| description | Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills |
| category | devops |
| risk | critical |
| source | community |
| source_repo | kubestellar/console |
| source_type | community |
| date_added | 2026-04-27 |
| author | kubestellar |
| tags | ["kubernetes","multi-cluster","mcp","dashboard","cncf","devops","observability"] |
| tools | ["claude","cursor","gemini","codex"] |
| license | Apache-2.0 |
| license_source | https://github.com/kubestellar/console/blob/main/LICENSE |
| plugin | {"setup":{"type":"manual","summary":"Requires kc-agent binary (brew tap kubestellar/tap && brew install kc-agent)","docs":"https://github.com/kubestellar/console#quick-start"}} |
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.
brew tap kubestellar/tap && brew install kc-agent
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.
The project ships with agent skills accessible via CLAUDE.md and AGENTS.md:
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.kc-agent uses. Start kc-agent only after switching KUBECONFIG/context to dedicated least-privilege credentials and verifying them.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
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.kc-agent on a public network without authentication.kc-agent) installed separately via Homebrew.