✨ Add KubeStellar Console agent

[clubanderson]

Add KubeStellar Console Agent

Adds a Copilot agent for KubeStellar Console, a multi-cluster Kubernetes dashboard with AI-powered operations.

Agent Overview

The KubeStellar Console Expert agent helps developers working on KubeStellar Console by providing domain-specific guidance on:

• Card development patterns — useCache/useCached* hooks, isDemoData/isRefreshing wiring, loading state management
• Array safety — guarding against undefined before .map()/.filter()/.join()
• Go backend — Fiber v2 handler patterns, multi-cluster goroutine patterns, demo mode checks
• Styling — Tailwind CSS with semantic color tokens, cn() utility
• i18n — all user-facing strings through react-i18next
• CNCF integrations — Argo CD, Kyverno, Istio, and 20+ more

About the Project

• License: Apache-2.0
• CNCF: Part of the KubeStellar CNCF Sandbox project
• Tech: Go backend (Fiber v2), React/TypeScript frontend (Tailwind CSS)
• MCP: Includes kc-agent MCP server for bridging kubeconfig to LLMs
• Website: https://console.kubestellar.io

[github-actions]

⚠️ This PR targets main, but PRs should target staged.

The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.

You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1514 --base staged

[Copilot]

Pull request overview

Adds a new custom Copilot agent definition for the KubeStellar Console project, expanding this repo’s catalog of reusable, domain-specific agents.

Changes:

• Added KubeStellar Console Expert agent with front matter (description/model/tools/name).
• Included guidance covering card patterns, caching hooks, Go/Fiber handler conventions, Tailwind theming, and i18n practices.

[Copilot]

New agent file was added under agents/, but it is not listed in docs/README.agents.md. Please add an entry (including the install links, consistent with the other rows) so the agent is discoverable and follows the repo’s documentation requirements for new files.

[clubanderson]

Addressed both review items:

1. ✅ Retargeted PR to staged branch (was main)
2. ✅ Added entry to docs/README.agents.md with VS Code and VS Code Insiders install links, placed alphabetically between Kotlin MCP and Kusto Assistant

Thanks for the review!

[github-actions]

🔍 Skill Validator Results

⛔ Findings need attention

Scope	Checked
Skills	1
Agents	1
Total	2
Severity	Count
---	---:
❌ Errors	2
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
❌	[agent:KubeStellar Console] Agent name 'KubeStellar Console' does not match filename 'kubestellar-console.agent.md' (expected 'KubeStellar Console.agent.md').
❌	[agent:KubeStellar Console] Agent name 'KubeStellar Console' contains invalid characters — must be lowercase alphanumeric and hyphens only.

Full validator output

```text Found 1 agent(s) ❌ [agent:KubeStellar Console] Agent name 'KubeStellar Console' does not match filename 'kubestellar-console.agent.md' (expected 'KubeStellar Console.agent.md'). ❌ [agent:KubeStellar Console] Agent name 'KubeStellar Console' contains invalid characters — must be lowercase alphanumeric and hyphens only. Validated 1 agent(s)

{Ansi.Red}Agent spec conformance failures — fix the errors above.{Ansi.Reset}

</details>
> **Note:** The validator returned a non-zero exit code. Please review the findings above before merge.

[aaronpowell]

It looks like you've incorrectly branched from the main branch not staged, and as a result all the materialised plugins are included in this PR.

You can attempt to fix this with a rebase:

git fetch origin staged
git rebase --onto origin/staged origin/main <branch name>
git push --force-with-lease

If that does not resolve it, you can run npm run plugin:clean which will delete the materialised plugins and you can commit that change.

[clubanderson]

Fixed! Rebased add-kubestellar-console onto upstream/staged using git rebase --onto upstream/staged 63d08d5. The PR now only contains our 2 files:

• agents/kubestellar-console.agent.md
• docs/README.agents.md

The extra 28 files from the chore: publish from staged commit have been removed.

[aaronpowell]

I'm a little confused on this agent, is it for people who are leveraging KubeStellar Console in the k8 projects they are working on, or for people contributing to KubeStellar Console? If it's the latter, I'm not sure the value of it being in the awesome copilot repo over the kubestellar/console repo, since it's a very narrow domain and not generally applicable.

[clubanderson]

Hi @aaronpowell — great question! The agent serves both audiences:

For users deploying/operating KubeStellar Console — helps with configuration, deploying via Helm, connecting clusters, using the MCP server (kc-agent) with Copilot, and integrating with CNCF tools like Argo CD and Kyverno.

For contributors to KubeStellar Console — the card development patterns, cache hook conventions, and Go backend rules are domain-specific enough that having them in a reusable agent config saves significant onboarding time.

The awesome-copilot listing makes it discoverable for both groups — contributors who find it here can drop it into their .github/copilot-instructions.md, and users exploring the Console ecosystem find it through the curated listing.

Also addressing the skill-validator errors in this push: renamed the agent name field from KubeStellar Console Expert → KubeStellar Console to match the kubestellar-console.agent.md filename convention. The validator should clear on the next run.

[aaronpowell]

I think a review of the agent needs to be undertaken as the first audience that you mention isn't one I see targeted by the agent, it reads very much like it's describing the coding standards and approaches for a contributor to the KubeStellar/console repo.

If it's meant to be for users of console, then I'd expect that it's helping with things like setting up the environment (like the decision on self-host vs sidecar), configuring kc-agent, working with the MCP server, etc.

[clubanderson]

Ran npm start locally and committed the regenerated docs/README.agents.md (the agent display name synced to match the front matter). CI should pass now — all 4 checks were green before this update, and this fixes the validate-readme failure. Ready for re-review! 🙏

[clubanderson]

Thanks for the clear guidance @aaronpowell! You're absolutely right — the original submission was contributor-focused (coding standards, hook patterns, build commands). I've completely rewritten it as an end-user operations guide for platform engineers and SREs who want to use the console.

The new agent covers:

• Getting started: hosted (console.kubestellar.io) vs self-hosted (Docker/Helm)
• kc-agent setup: the local MCP server that bridges kubeconfig to AI assistants — with install commands
• Cluster connections: adding clusters, validating contexts, diagnosing offline states
• AI-assisted operations: querying pods/deployments/events via natural language chat
• Deploy missions: guided CNCF project installs (Argo CD, Kyverno, Istio)
• Troubleshooting: common connectivity and auth issues

The description now reflects this user audience. Ready for re-review!